This repository has been archived by the owner on Oct 9, 2018. It is now read-only.
873313 - Very high memory usage during repo sync #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Squashed commit of the following: commit 2c9f89b Author: John Matthews <jwmatthews@gmail.com> Date: Mon Mar 18 10:41:34 2013 -0400 Defined SUCCESS, in terms of when an item has downloaded successfully commit 8f2ec41 Author: John Matthews <jwmatthews@gmail.com> Date: Mon Mar 18 10:40:51 2013 -0400 Update Callback to communicate more information about an item that has completed commit 49a1582 Author: John Matthews <jwmatthews@gmail.com> Date: Mon Mar 18 10:40:11 2013 -0400 Removed xml snippets from each rpm item
|
This request is not to be merged until after 2.1 is released. It will be in our 2.1.1 release. |
ghost
assigned
jdob
pushed a commit
that referenced
this pull request
Apr 8, 2013
873313 - Very high memory usage during repo sync
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fix removes the lookup of yum package metadata from grinder.
For rhel 6.2 the lookup was taking ~5 mins...yet transferring that data over activeobject to the original caller was taking from 15-30 minutes.
This logic is being moved into Pulp's YumImporter.