Issue: geopoints loading takes long for complex sparql queries
Investigate
[] Why does it take so long to load?
[] Evaluate possible solutions and identify the pro/cons of each direction, including what other problems could be solved in addition
Possible solutions
1. Cache the results of SPARQL requests in a local database for a day or so. SPARQL should take care of it’s own result caching and does already, but it doesn’t
2. Cache the final GeoJSON results in a local database for a day or so.
3. Do the query only on page parsing see {T322353}
- Has the advantage that purging is a solved concept
- Issue: page rendering (also preview) will take a long time
- Page rendering in steps (not available yet, but discussed, see T282585)
- Parser already has a fall back to go for a stale version when loading is too long
- Most pages won't have very complex, slow queries.
- Risk: What if rendering the map fails?
Timebox: 8