HrefPrnFieldMixin has a high performance impact
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Describe the bug
HrefPrnFieldMixin shows up prominently in profiling up package upload. The reversing / resolution part specifically - lots of time is spent in Django's URL handling stack.
https://github.com/pulp/pulpcore/blob/main/pulpcore/app/serializers/base.py#L66-L80
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with pulpcore/app/serializers/base.py lines 66-80 and profile package upload to confirm the reversing and resolution cost attributed to HrefPrnFieldMixin. Trace the Django URL handling calls involved and identify a measurable way to reduce their impact. The issue names no test or specific target behavior, so completion criteria need to be established from the profiling results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100