[
https://issues.apache.org/jira/browse/JENA-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369518#comment-15369518
]
ASF GitHub Bot commented on JENA-626:
-------------------------------------
Github user afs commented on the issue:
https://github.com/apache/jena/pull/95
Another use case:
In my day-job, we have a local (same JVM) database because calling to a
remote database (even same datacenter) is too expensive. RDF is used to drive
the UI for HTTP/HTML requests. This means we get a lot of small calls into the
database for every single HTTP request. Going off machine for each call does
not work. Getting larger parts of the RDF (i.e. a few large remote calls) only
gets us into having a local graph and many calls to that.
We can of course add our own caching because we control the whole stack but
it suggests a design whereby caching is done by the `QueryExecution` and not as
part of Fuseki HTTP request handling, either specific to Fuseki or as a general
feature in ARQ.
> SPARQL Query Caching
> --------------------
>
> Key: JENA-626
> URL: https://issues.apache.org/jira/browse/JENA-626
> Project: Apache Jena
> Issue Type: Improvement
> Reporter: Andy Seaborne
> Assignee: Saikat Maitra
> Labels: java, linked_data, rdf, sparql
>
> Add a caching layer to Fuseki to cache the results of SPARQL Query requests.
> This cache should allow for in-memory and disk-based caching, configuration
> and cache management, and coordination with data modification.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
