PLAT-723 - pymongo 3.0.3 migration #8985
Closed
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.
My first pass at https://openedx.atlassian.net/browse/PLAT-723
While running the tests on this upgrade I have noticed that CPU usage inside of devstack has increased by about 2x. I was seeing CPU usage of around 89-100% with pymongo 2.7. With the upgrade I'm seeing cpu usage of around 150-200%.
Some of the unit tests seem like they take a (very) long to complete such as:
test_container_get_query_count_3__3__30_ (cms.djangoapps.contentstore.views.tests.test_item.GetItemTest) ... #5
I am hoping that this PR will functionally fix everything that needs to be updated for the pymongo 3.0.3 upgrade. The app still needs to be load tested to verify that this is a good release.
Will also need to pull in edx/edx-platform/pull/8980 which will hopefully improve the speed of the testing.