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

Optimise database queries #47

Open
pverscha opened this issue Aug 28, 2024 · 1 comment
Open

Optimise database queries #47

pverscha opened this issue Aug 28, 2024 · 1 comment

Comments

@pverscha
Copy link
Member

Right now, the API performs some database queries to get a list of all proteins with a specific accession number. Our API, however, requests too much information from the database, and does not split the SQL-query in smaller chunks. For one of the examples that I'm currently benchmarking, it tries to query 83k proteins at the same time causing a significant slowdown of the database.

For some endpoints, like pept2prot we also don't need to retrieve all columns from the database. By querying in a better-informed manner, we should be able to significantly speed up the process.

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

No branches or pull requests

2 participants
@pverscha and others