Actions
Issue #3903
closedRedundant solver instantiated and loaded during a recursive associate call
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
2.17.0
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Sprint 41
Quarter:
Description
It seems a solver is being unnecessarily instantiated and loaded in a recursive associate call
This wastes a lot of RAM and CPU with big repositories and might be avoided.
Updated by milan over 6 years ago
- Status changed from NEW to POST
- Assignee set to milan
Just created a PR to address this: https://pulp.plan.io/issues/3903
Updated by CodeHeeler over 6 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 41
Added by milan over 6 years ago
Updated by milan over 6 years ago
- Status changed from POST to MODIFIED
Applied in changeset 3a42248db2de6c2bc92bfd5ada8880947a40b426.
Updated by ipanova@redhat.com over 6 years ago
- Sprint/Milestone set to 2.17.0
- Platform Release set to 2.17.0
Updated by ipanova@redhat.com over 6 years ago
- Status changed from MODIFIED to 5
Updated by ipanova@redhat.com about 6 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
Actions
Share solver between recursive associate calls
Currently each associate call in a recursive tree of calls instantiates and loads its own instance of a solver. This is both CPU and RAM expensive.
The fix avoids subsequent instantiation of the solver thru passing it as an argument of the associate function.
Fixes: #3903