Bug 872190
Summary: | Very high memory usage during repo sync | |||
---|---|---|---|---|
Product: | [Retired] Pulp | Reporter: | Preethi Thomas <pthomas> | |
Component: | rpm-support | Assignee: | Pradeep Kilambi <pkilambi> | |
Status: | CLOSED NOTABUG | QA Contact: | Preethi Thomas <pthomas> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | Master | CC: | jason.dobies, mhrivnak, pkilambi, rbarlow, skarmark | |
Target Milestone: | --- | Keywords: | Triaged | |
Target Release: | Sprint 42 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 873313 (view as bug list) | Environment: | ||
Last Closed: | 2012-11-27 19:26:44 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 873313 |
Description
Preethi Thomas
2012-11-01 14:15:23 UTC
I also experienced this bug when trying to synchronize with the Red Hat CDN for RHEL 6. My system used ~3 GB and then failed due to exhaustion of memory. I am able to attribute the excessive memory use to grinder. Specifically, this change increased memory use by at least 10x: http://git.fedorahosted.org/cgit/grinder.git/commit/?id=5727f5238b3202177a62687a97335092128731d6 You can duplicate this by doing the following in a python shell: >>> from grinder.YumInfo import YumMetadataObj >>> y = YumMetadataObj('reposci', 'http://ftp1.scientificlinux.org/linux/scientific/6x/x86_64/updates/security/') >>> x = y.getDownloadItems() You will see the python process using ~240MB of RAM, which is exactly what you see pulp do during a repo sync, at the end of the metadata retrieval stage. It's even easier to isolate because grinder spawns a new python process to do the metadata fetching, which is shown with PID 22161 in Preethi's output above. In her second example, you can see it with "243m" in the "RES" column. Closing out the master version of this, it's being handled in 2.0. |