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.

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

ZOOKEEPER-2835: Run server with `-XX:+AlwaysPreTouch` jvm flag #301

Open
wants to merge 1 commit into
base: master
from

Conversation

Projects
None yet
2 participants
@asdf2014
Member

asdf2014 commented Jul 4, 2017

Add -XX:+AlwaysPreTouch jvm flag for server, let jvm through demand-zeroed way to allocate memory once in place when the process started.

@afine

This comment has been minimized.

Contributor

afine commented Aug 3, 2017

I'm not sure if we should make this default configuration since it should increase startup time and will only increase performance for users with larger memory requirements. Our current default -XX args are pretty conservative and we don't really have any performance related switches there. Perhaps we should document this as a recommendation rather than making this default?

@asdf2014

This comment has been minimized.

Member

asdf2014 commented Aug 4, 2017

Hi @afine . Thanks for your comments. Your consider is entirely correct. But I found the PR#16937 from elasticsearch. And every node in our elasticsearch cluster always be set as huge ES_HEAP_SIZE value. Then it just spend a few second when the elasticsearch instance start up. However, the server node in zookeeper cluster usually we don't assign too large memory. So, the zookeeper as daemon instance will get more benefit from it. (PS, same tuning in Cassandra, Jenkins etc.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment