Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance issue with package details endpoint #1502

Open
p-brito opened this issue Jan 29, 2025 · 2 comments
Open

Performance issue with package details endpoint #1502

p-brito opened this issue Jan 29, 2025 · 2 comments

Comments

@p-brito
Copy link

p-brito commented Jan 29, 2025

While attempting to retrieve details for this package (https://repo.packagist.org/p2/letraceursnork/wordpress-security-advisories~dev.json), I encountered significant performance issues due to the sheer volume of conflict data. The last successful request I managed to execute returned a response exceeding 5 million lines, making the request nearly impossible to complete efficiently. To improve accessibility and performance, I suggest removing conflict information from the main endpoint and introducing a dedicated endpoint specifically for fetching this data.

@stof
Copy link
Contributor

stof commented Jan 31, 2025

Those p2 endpoints are the ones used by Composer to read the metadata it needs to resolve dependencies. Removing the conflict data from them would break things, because it would effectively remove the conflicts from the package definition.

@stof
Copy link
Contributor

stof commented Jan 31, 2025

this package specifically has a huge file here, because it has tons of conflicts while also having 470 branches included in this file (and the composer-specific minification does not help a lot, because those conflict rules are changing between versions, and the branches don't even have name that sort them in a relevant order minimizing back and forth changes)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants