-
Notifications
You must be signed in to change notification settings - Fork 18
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
RAM memory is not free #15
Comments
I'll take a look when I have time. I had valgrind running with no memory leaks but it's been a long time. I'm sure there could be leaks now. pm2 as far as I know is a npm project.
|
Hi @fikisipi ,
I know in general your lib can find a better result than the above LKH lib but it faces the issue with the RAM so that i cannot use it stable. Please support to investigate and correct the issue. If you need any info, don't hesitate to ask me. Thanks |
@fikisipi Hi, is there any update from your side? I'd love to use your lib but we need to resolve the above issue first. |
Hi @fikisipi If using multiprocessing, it doesn't have any problems with the memory issue, It only happens when i use asyncio. |
When I run elkai with a large number of tests, I see that the RAM memory increases and is not free. So when the RAM memory reaches the maximum of computer RAM (64GB/128BM) it must be restarted to free memory to be able to run.
As you can see in the above photo, i run 2 instances with pm2, 1 instance uses 26.6GB, the other has to restart 1 (The curved arrow icon column) to free the memory so that it can be run again.
The text was updated successfully, but these errors were encountered: