-
-
Notifications
You must be signed in to change notification settings - Fork 461
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 file: Dockerfile-jemalloc #366
base: master
Are you sure you want to change the base?
Conversation
Can you please provide some additional information about the underlying issue and how does |
Some have identified This PR should probably document somewhere such as the README about why Probably would be good if someone verifies with a before & after result of the Dockerfile resolving the issue too. |
@polarathene I'm curious if I should pull this into our current fork, can you provide some benchmarks, as well as docker stats if possible? |
@polarathene Also there was a small update to the docker file to upgrade to golang 1.17, can you merge them in here too? |
@angelo-hub I'm not the author of this PR, I do not use imaginary. My comment was added when I was looking at the project among others, I saw this PR and thought I'd pass some information along at the time. I have no time available for contributions sorry :( |
@angelo-hub do you maintain a more recent fork/build of imaginary? |
Add the Dockerfile-jemalloc file to build the imaginary of jemalloc. solve the memory leak problem