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.

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

Add clarification: min_mem_size and max_mem_size = NULL/None in h2o.init() uses JVM default #8187

Closed
exalate-issue-sync bot opened this issue May 11, 2023 · 1 comment
Assignees

Comments

@exalate-issue-sync
Copy link

Specify in documentation that when launching an H2O cluster ({{h2o.init()}}), if {{min_mem_size}} and {{max_mem_size}} are not defined, ({{-Xmx}} for command line) then H2O will allocate memory determined by default memory of Java Virtual Machine (JVM). The amount is dependent on the Java version, but generally 25% of the machine's physical memory.

H2O 3 docs - [http://docs.h2o.ai/h2o/latest-stable/h2o-docs/starting-h2o.html|http://docs.h2o.ai/h2o/latest-stable/h2o-docs/starting-h2o.html]
R docs - [http://docs.h2o.ai/h2o/latest-stable/h2o-r/docs/reference/h2o.init.html|http://docs.h2o.ai/h2o/latest-stable/h2o-r/docs/reference/h2o.init.html]
Python docs - [http://docs.h2o.ai/h2o/latest-stable/h2o-py/docs/h2o.html?highlight=init#h2o.init|http://docs.h2o.ai/h2o/latest-stable/h2o-py/docs/h2o.html?highlight=init#h2o.init]

@h2o-ops
Copy link
Collaborator

h2o-ops commented May 14, 2023

JIRA Issue Migration Info

Jira Issue: PUBDEV-7451
Assignee: hannah.tillman
Reporter: Neema Mashayekhi
State: Resolved
Fix Version: 3.30.0.2
Attachments: N/A
Development PRs: Available

Linked PRs from JIRA

#4527

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

No branches or pull requests

2 participants