-
Notifications
You must be signed in to change notification settings - Fork 155
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
[1.3.1] Large Object Handler may consume much memory and causes oom eventually #570
Comments
InvestigationTake Log of Memory Usage and Stack Trace of every processes in
use of
|
use of
|
Multipart, No Traffic ShapingDetailed benchmark will be done and reported at https://github.com/leo-project/notes |
Memory Leak from
|
@windkit Thanks for testing it. I've recognized we fixed this issue. |
Description
To solve issue #506, we added the "work pool" approach to limit the memory usage in
leo_gateway
.While preliminary testing shows it can limit the memory usage, further long testing reveals problems of ever growing memory usage
Observation
Use
parallel
to launch64
instances ofs3cmd
to upload256MB
fileMemory usage slowly increases over time and with a long test (e.g.
10240
), all memory/swap were used up andleo_gateway
was killed withoom
The text was updated successfully, but these errors were encountered: