You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
💡 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).
With the current DB settings, data import service runs slow, find a way to optimize it. A possible solution is MySQL bulk load.
The text was updated successfully, but these errors were encountered: