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
Originally reported by: Marcel Bollmann (Bitbucket: mbollmann, GitHub: mbollmann)
Users report that retrieving lemma suggestions can sometimes take up to 7 seconds, which is huge.
The testing script introduced in commit 1e1f888 suggests that the part which retrieves lemma suggestions from other texts within the project (with the same "ascii" token) is a major bottleneck, taking almost a full second for one lookup on the production database.
If there is no evidence for other factors, refactoring this lookup should be considered.
A possible solution could be to introduce another database table which maps (project_id, mod_ascii) pairs to tag_ids of lemma annotations. This table would have to be updated whenever lemma annotations are saved, and could then be used for efficient lookup during retrieval.
Originally reported by: Marcel Bollmann (Bitbucket: mbollmann, GitHub: mbollmann)
Users report that retrieving lemma suggestions can sometimes take up to 7 seconds, which is huge.
The testing script introduced in commit 1e1f888 suggests that the part which retrieves lemma suggestions from other texts within the project (with the same "ascii" token) is a major bottleneck, taking almost a full second for one lookup on the production database.
If there is no evidence for other factors, refactoring this lookup should be considered.
A possible solution could be to introduce another database table which maps
(project_id, mod_ascii)
pairs totag_id
s of lemma annotations. This table would have to be updated whenever lemma annotations are saved, and could then be used for efficient lookup during retrieval.The text was updated successfully, but these errors were encountered: