search

hitontology / gui

Erneuerung der Benutzungsoberflächen von HITO
https://hitontology.github.io/gui/
MIT License
0 stars 0 forks source link

Possibly cache SPARQL query results for faster responses & less server load #35

Closed Yagnap closed 4 months ago

Yagnap commented 7 months ago

We could cache the results of every SPARQL query (for session/short time (something like two hours?) only) so if the same query is tried multiple times the server isn't used too much and the user possibly gets faster response time because they don't need to wait for the SPARQL query to finish again. But may need to much time to implement for too little benefit.

KonradHoeffner commented 7 months ago

Virtuoso SPARQL should already do some caching at the SQL level but for local caching we could use localStorage. However then we would need to take care not to use outdated results, but as HITO doesn't change much it could be an option.

However I think the most time consuming step for the user are just the SPARQL queries at the start where the count of each property is selected. We could either merge that into a single query or just bake it into js/edges.js. The whole edges.js could probably be automatically generated anyways given a list of keys.