-
Notifications
You must be signed in to change notification settings - Fork 0
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
Open Ethno reported slowing down. Can it be a matter of intensity of coding? #226
Comments
I don't see how this could have become slower in recent weeks, but I know that loading long lists of codes has always been slow (has not yet been optimized at all). |
Excellent Daniel, thank you so much. |
Done. Now only the top-level of codes are initially loaded from the server. This improves the response time from 9s to < 1s. A codes subtree is only loaded from the server when a code is clicked. |
Thanks, Daniel. It is indeed very fast now, though the increase in performance is predicated on ethnographers using hierarchies. The POPREBEL team is big on hierarchies, but subsequent projects might adopt a flatter approach. Anyway, we have the ethnographers meeting later today, I will inform them and get back to you if needed. |
Flatter hierarchies (like thousands of codes at the top-level) is also no problem as then pagination is used. Not more than 100 codes at the top-level are displayed on one page. If there are more they are displayed on several pages. |
This is a question for @damingo and, as a fallback, to @tanius.
POPREBEL ethnographers report a much slower performance of OpenEthno lately (three weeks). Is it possible, they wonder, that this is an artifact of the number of codes proliferating? I would be surprised, if that was the case, because this is just text and computers can do text. Are you aware of any other problem that might have occurred?
From Wojciech:
For me, loading https://edgeryders.eu/annotator/codes?discourse_tag=ethno-poprebel takes about 3 seconds.
Again from Wojciech:
The text was updated successfully, but these errors were encountered: