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

Let the user choose a custom heap on the wrapper script. #4

Merged
merged 1 commit into from May 21, 2022

Conversation

zeehio
Copy link
Contributor

@zeehio zeehio commented Mar 4, 2021

First of all, thank you for your work :-)

With this commit, the user can define an environment variable MIRTRACE_HEAP_ALLOCATION="8GB" to
let the mirtrace wrapper script know that it should use that amount of
RAM for the JVM heap.

The default (when MIRTRACE_HEAP_ALLOCATION is not defined) is to use
half of the RAM as before.

I chose to use an environment variable instead of an argument because arguments are passed over to the java subprocess and filtering them would increase complexity.

With this commit, the user can define MIRTRACE_HEAP_ALLOCATION="8GB" to
let the mirtrace wrapper script know that it should use that amount of
RAM for the JVM heap.

The default (when MIRTRACE_HEAP_ALLOCATION is not defined) is to use
half of the RAM as before.
@yrin yrin merged commit 87a50b8 into friedlanderlab:master May 21, 2022
@yrin
Copy link
Contributor

yrin commented May 21, 2022

Thank you for your patch! I think it's a good solution. Sorry about the delay in merging. At some point later on I will release an updated build with this update included.

@zeehio
Copy link
Contributor Author

zeehio commented May 21, 2022

Looking forward to the next release! Thanks!

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

Successfully merging this pull request may close these issues.

None yet

2 participants