-
Notifications
You must be signed in to change notification settings - Fork 3
OBO Dashboard stopped working within reasonable time and memory constraints #87
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
Comments
I suggest skipping the big ones in the meantime. NCIT, NCBITaxon, and ChEBI aren't curated/created in a normal way anyway |
@matentzn is this reproducible by running |
by the way, what's the impact? http://dashboard.obofoundry.org/dashboard/index.html looks fine? |
Also, ROBOT 1.9.1 added the code in this PR, some of the comments mention a performance hit. I wonder if that's why you're experiencing problems |
Yea, it failed again, with the increased memory and time constraints. |
@erik-whiting we cannot re-run it at the moment (update) |
We have a bit of a problem; for some reason, we cannot run the OBO dashboard anymore; NCIT and friends of similar size stopped being processable. Before ROBOT 1.9.0, it was still possible to run OBO Dashboard with 48GB or memory, and a timeout of 2 hours per ontology. Now, we cannot run it at all anymore (not even with 55 GB memory and 4 hours timeout).
Its the timeout that kicks in, not an out of memory error; but 4 hours is already a lot for an ontology.
I will try now with 56 GB memory which is the absolute maximum I have on my machine, and an 8 hour timeout.
Any ideas of how we can deal with this is very appreciated.
PS: my guess is the problem is ROBOT report, but it could also be ROBOT reason - I cannot see it in the log unfortunately.
The text was updated successfully, but these errors were encountered: