Bug #13607
open
[arv-mount] avoid excessive memory consumption of idle arv-mounts
Description
I noticed several arv-mounts killed
$ dmesg | grep 'Out of' [11983650.641067] Out of memory: Kill process 101941 (python3) score 420 or sacrifice child [11983650.708218] Out of memory: Kill process 101941 (python3) score 420 or sacrifice child [11983651.444473] Out of memory: Kill process 101941 (python3) score 420 or sacrifice child
then I noticed that some simple "ls" on the keep mount will make a load of 1 and it was unable to exit. them memory ballooning is caused by 90 days old arv-mounts that had no use in the last 89 days.
Is there a way to shrink the memory usage in arv-mount that are idle?
Updated by Nico César almost 6 years ago
- Category set to FUSE
- Target version set to To Be Groomed
Updated by Nico César almost 6 years ago
- Subject changed from [arv-mount] to [arv-mount] avoind excesive memory consumption of idle arv-mounts
Updated by Peter Amstutz almost 6 years ago
It says it is killing python3 but I don't think the FUSE mount is using python3?
Updated by Peter Amstutz almost 6 years ago
Separately from the soft memory limits it uses to clear the cache, it keeps the last 4 collections hot in the cache (regardless of how much memory they take up). We could release those if the mount has been idle for a while, but only if the kernel cache has forgotten them as well.
If we had stable inode numbering (#12664) then we could release things from the cache regardless of whether the kernel is still hanging on to it or not.
We could greatly reduce the overall footprint with incremental manifest loading (#12314), but that comes with complexity costs.
Updated by Tom Clegg almost 6 years ago
- Subject changed from [arv-mount] avoind excesive memory consumption of idle arv-mounts to [arv-mount] avoid excessive memory consumption of idle arv-mounts
Updated by Peter Amstutz almost 3 years ago
- Target version deleted (
To Be Groomed)