Closed MGlauer closed 1 month ago
It never took longer than 20 sec. for me, but it still takes far too long.
I assume we can improve this by using the cpython implementation of the owl parser. I assume Python is just slow. It reads the files from the oeo release that are stored locally on the server. We will try this soon. There is this warning showing up:
* Owlready2 * Warning: optimized Cython parser module 'owlready2_optimized' is not available, defaulting to slower Python implementation
Also a good point is to cache this on the server side and only update it once a new oeo version is added.
Description of the issue
Loading of the ontology page takes more than a minute. This is quite a bad first impression for first-time users and will likely drive them away.
Steps to Reproduce
Ideas of solution
I do not know what is taking so long. Once loaded, the page shows an overview of the modules. The slowdown seems to not occur on the client-side (I stopped the JS execution and the loading finished immediately upon resuming), but on the server side. So, I guess the server is loading something from somewhere that is just cached on the client-side, but not on the server side. As the request does not have any parameters, it is not immediately apparent, why this is necessary.
Context and Environment
Workflow checklist