Open rubensworks opened 2 years ago
Currently, we configure our document's cache (LRU) to have a size of 2048: https://github.com/comunica/comunica-feature-link-traversal/blob/master/engines/config-query-sparql-link-traversal/config/rdf-resolve-quad-pattern/actors/hypermedia.json#L13
This is quite arbitrary, and ignores things like file size and how well they apply to query results.
We should introduce better caching techniques dedicated to link traversal.
Example query where this cache is relevant: https://comunica.github.io/comunica-feature-link-traversal-web-clients/builds/solid-default/#datasources=https%3A%2F%2Fdrive.verborgh.org%2Fmovies%2F&query=PREFIX%20schema%3A%20%3Chttps%3A%2F%2Fschema.org%2F%3E%0ASELECT%20*%20WHERE%20%7B%0A%20%20%3Fmovie%20a%20schema%3AMovie.%0A%20%20%3Faction%20a%20schema%3AWatchAction%3B%0A%20%20%20%20%20%20%20%20%20%20schema%3Aobject%20%3Fmovie.%0A%7D&solidIdp=https%3A%2F%2Fdrive.verborgh.org%2F
Thanks for the suggestion!
Issue type:
Description:
Currently, we configure our document's cache (LRU) to have a size of 2048: https://github.com/comunica/comunica-feature-link-traversal/blob/master/engines/config-query-sparql-link-traversal/config/rdf-resolve-quad-pattern/actors/hypermedia.json#L13
This is quite arbitrary, and ignores things like file size and how well they apply to query results.
We should introduce better caching techniques dedicated to link traversal.
Example query where this cache is relevant: https://comunica.github.io/comunica-feature-link-traversal-web-clients/builds/solid-default/#datasources=https%3A%2F%2Fdrive.verborgh.org%2Fmovies%2F&query=PREFIX%20schema%3A%20%3Chttps%3A%2F%2Fschema.org%2F%3E%0ASELECT%20*%20WHERE%20%7B%0A%20%20%3Fmovie%20a%20schema%3AMovie.%0A%20%20%3Faction%20a%20schema%3AWatchAction%3B%0A%20%20%20%20%20%20%20%20%20%20schema%3Aobject%20%3Fmovie.%0A%7D&solidIdp=https%3A%2F%2Fdrive.verborgh.org%2F