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

Commit 497afcf

Browse files
author
troutman_margaret@yahoo.com
committed
Edited 510_Deployment/20_hardware.asciidoc with Atlas code editor
1 parent 18f325a commit 497afcf

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

510_Deployment/20_hardware.asciidoc

+2-2
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
[[hardware]]
22
=== Hardware
33

4-
If you've been following the normal development path, you've probably been playing
4+
If you've been following the normal development path, you've probably been playing((("deployment", "hardware")))((("hardware")))
55
with Elasticsearch on your laptop, or a small cluster of machines laying around.
66
But when it comes time to deploy Elasticsearch to production, there are a few
77
recommendations that you should consider. Nothing is a hard-and-fast rule;
@@ -11,7 +11,7 @@ production clusters
1111

1212
==== Memory
1313

14-
If there is one resource that you will run out of first, it will likely be memory.
14+
If there is one resource that you will run out of first, it will likely be memory.((("hardware", "memory")))((("memory")))
1515
Sorting and aggregations can both be memory hungry, so enough heap space to
1616
accommodate these are important. Even when the heap is comparatively small,
1717
extra memory can be given to the OS file system cache. Because many data structures

0 commit comments

Comments
 (0)