Project

Profile

Help

Task #2780

closed

Investigate memory issues with mongoengine 0.13+

Added by ttereshc almost 7 years ago. Updated almost 4 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

Even just restarting Pulp services with mongoengine 0.13 results in noticeable (400-700MB) increase of memory consumption in comparison to older versions of mongoengine. Investigation needed.

0.13 is not in Fedora yet, Fedora 27 currently contains python-mongoengine 0.12.
https://apps.fedoraproject.org/packages/python-mongoengine/overview/

The outcome of this task depends on the investigation results but I expect it to be one of the following:
- either mongoengine version restriction
- or note in docs that 0.13 consumes more memory
- or fix to the Pulp code if high memory consumption is caused by a certain use case which we can change in a backward compatible way to continue support of older mongoengine versions.

Upd: I think it is worth testing the most recent mongoengine, though I do not see 0.14 on PyPI at the moment.

https://github.com/MongoEngine/mongoengine/releases/tag/v0.14.0

Actions #1

Updated by ipanova@redhat.com almost 7 years ago

Just a small note that 0.14 is already out, that means, 0.13 will not get into Fedora

Actions #2

Updated by ttereshc almost 7 years ago

  • Subject changed from Investigate memory issues with mongoengine 0.13 to Investigate memory issues with mongoengine 0.13+
  • Description updated (diff)
Actions #3

Updated by ipanova@redhat.com almost 7 years ago

  • Description updated (diff)
Actions #4

Updated by ipanova@redhat.com almost 7 years ago

i went through this and i think this it is ready to be marked as groomed.

Actions #5

Updated by bmbouter almost 7 years ago

I want to share two thoughts about this issue.

  • While this is regretable I think practically it will only impact a Pulp running on a future version of Fedora. With that limited impact I think not fixing this bug would be OK.
  • If this is investigated, I think we need to understand if Pulp is doing something wrong or if its a mongoengine regression. Has this bug been filed with upstream mongoengine? Maybe we could reduce Pulp's usage of mongoengine to a simpler reproducer that proves Pulp isn't creating the problem (or that it is).
Actions #6

Updated by ipanova@redhat.com almost 7 years ago

  • Groomed changed from No to Yes
Actions #7

Updated by bmbouter about 5 years ago

  • Status changed from NEW to CLOSED - WONTFIX
Actions #8

Updated by bmbouter about 5 years ago

Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.

Actions #9

Updated by bmbouter about 5 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF