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

default data import is too slow #2

Open
onursumer opened this issue Apr 20, 2016 · 1 comment
Open

default data import is too slow #2

onursumer opened this issue Apr 20, 2016 · 1 comment

Comments

@onursumer
Copy link
Member

With the current DB settings, data import service runs slow, find a way to optimize it. A possible solution is MySQL bulk load.

@pieterlukasse
Copy link
Collaborator

💡 can we maybe improve performance by getting rid of the table pdb_uniprot_residue_mapping? If we store a standard alignment string pdb_uniprot_alignment (and this seems to be the case now - see all the *_ALIGN fields in table pdb_uniprot_alignment) it should be much faster. The table pdb_uniprot_residue_mapping is huge (like ~220M records) and will only grow if we want to support ensembl, uniprot and maybe others....

If the alignment string is stored, the residue mapping can be generated on the fly (either on frontend or backend).

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

3 participants