pulp / pulp/pulp_ansible

As a user I have efficient collections endpoint

Open
#720 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

GalaxyNG Migrated from Redmine Story
Dominant language
Python
Stars
68
Forks
62
Avg merge
1d 14h
Merged PRs (30d)
37

Description

Author: @fao89 (fao89)

Redmine Issue: 8262, https://pulp.plan.io/issues/8262


Currently, the collections endpoint provides data from multiple tables which can harm the performance, as the query is done for every request.

We need to pre-compute the query to improve the performance

Context: https://github.com/pulp/pulp_ansible/pull/469/files#r573247512

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the collections endpoint and review the query behavior described in the issue, then read the referenced pulp_ansible pull request discussion for context. Done means the endpoint uses pre-computed data instead of querying multiple tables on every request, with the performance impact verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
ansible, python
Domain
api, backend, performance
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.