Skip to content
This repository was archived by the owner on Sep 21, 2021. It is now read-only.

Commit e04437c

Browse files
committed
Edited 510_Deployment/20_hardware.asciidoc with Atlas code editor
1 parent c119f82 commit e04437c

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

510_Deployment/20_hardware.asciidoc

+4-4
Original file line numberDiff line numberDiff line change
@@ -18,9 +18,9 @@ extra memory can be given to the OS filesystem cache. Because many data structu
1818
used by Lucene are disk-based formats, Elasticsearch leverages the OS cache to
1919
great effect.
2020

21-
A machine with 64GB of RAM is the ideal sweet spot, but 32GB and 16GB machines
22-
are also common. Less than 8GB tends to be counterproductive (you end up
23-
needing many, many small machines), and greater than 64GB has problems that we will
21+
A machine with 64 GB of RAM is the ideal sweet spot, but 32 GB and 16 GB machines
22+
are also common. Less than 8 GB tends to be counterproductive (you end up
23+
needing many, many small machines), and greater than 64 GB has problems that we will
2424
discuss in <<heap-sizing>>.
2525

2626
==== CPUs
@@ -83,7 +83,7 @@ point of failure.
8383
A fast and reliable network is obviously important to performance in a distributed((("hardware", "network")))((("network")))
8484
system. Low latency helps ensure that nodes can communicate easily, while
8585
high bandwidth helps shard movement and recovery. Modern data-center networking
86-
(1GbE, 10GbE) is sufficient for the vast majority of clusters.
86+
(1 GbE, 10 GbE) is sufficient for the vast majority of clusters.
8787

8888
Avoid clusters that span multiple data centers, even if the data centers are
8989
colocated in close proximity. Definitely avoid clusters that span large geographic

0 commit comments

Comments
 (0)