Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Increase default heap size to 2g #18311

Merged
merged 2 commits into from May 14, 2016
Merged

Increase default heap size to 2g #18311

merged 2 commits into from May 14, 2016

Commits on May 13, 2016

  1. Increase default heap size to 2g 

    Benchmarking with the geonames data set shows that Elasticsearch truly
needs 2g of heap or the heap is a bottleneck for indexing rates. If our
goal is to satisfy the out-of-the-box-experience, we should prioritize
the out-of-the-box performance experience. Thus, the default heap should
be 2g until smaller heaps are not the bottleneck for indexing small data
sets.
    @jasontedor
    jasontedor committed May 13, 2016
    Configuration menu
    Copy the full SHA
    52b09bc View commit details
    Browse the repository at this point in the history

  2. Restore unequal min and max default heap 

    After considerable discussion, we have elected to set the default min
heap to 256m and the default max heap to 2g. This is to balance the
desire for a good out-of-the-box performance experience (default max
heap of 2g) with a good out-of-the-box experience running on machines
with limited resources or running multiple instances on a single modern
developer laptop (default min heap of 1g).
    @jasontedor
    jasontedor committed May 13, 2016
    Configuration menu
    Copy the full SHA
    bc46517 View commit details
    Browse the repository at this point in the history