Summary: | sys-apps/portage-2.2_rc8 eats huge amounts of memory on --depclean | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Volker Hemmann <volkerarmin> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | esigra, rogerx.oss, tiago, zeekec |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 240320, 210077 |
Description
Volker Hemmann
2008-09-04 21:23:07 UTC
I've been monitoring memory consumption for the past month here and finally realized, it's Portage who's caching large amounts of memory here. Although, ATop doesn't slate Portage (Python) as using the memory. But after syncing and/or compiling (using Portage/Python), large amounts of memory are apparently consumed by comparing "free -m" output. (I've finally concluded this after dropping to tty and DWM!) My best guess, it's Python and/or un-optimized Python coding. Might be a function or two in Portage not optimized to make proper use of CPU/Memory resources?? The --depclean-lib-check code (enabled by default) used to consume lots of memory when looking up owwners when there were lots of libraries to uninstall. It's been fixed to avoid consuming so much memory, but it can be very time consuming. You can use --depclean-lib-check=n to disable it. So can we close this? (In reply to comment #2) > The --depclean-lib-check code (enabled by default) used to consume lots of > memory when looking up owwners when there were lots of libraries to uninstall. > It's been fixed to avoid consuming so much memory, but it can be very time > consuming. You can use --depclean-lib-check=n to disable it. (In reply to comment #3) > So can we close this? Yes, this we can consider this fixed now that. Note that the --depclean-lib-check code is disabled automatically when preserve-libs is enabled, since the fix for bug 286714: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=c64d4abee145d083c70273be8fd23bd56dffe7ec Also, the --depclean-lib-check (and preserve-libs) code now uses a more efficient method to look up the owners of libraries and consumers: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=f393413c3f823ef4a60acfcc41c3920933510fc1 FYI: emerge: error: no such option: --depclean-lib-check (In reply to comment #5) > FYI: emerge: error: no such option: --depclean-lib-check Currently, it's only available in portage-2.2.x. |