[
https://issues.apache.org/jira/browse/JENA-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249775#comment-15249775
]
ASF GitHub Bot commented on JENA-626:
-------------------------------------
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/95#issuecomment-212405267
Another +1 to @osma's comments. In re: serialization: it seems to me that
the need here is for "replay-ability". Certainly serialization will do that,
but at a very high cost, and the cost will vary with client behavior (suppose
everyone asks for RDF/XML vs. everyone asks for Turtle). There are cheaper ways
to get "rewindable-ity", such as have been mentioned (`ResultSetRewindable`).
Recently, @afs did work with node caching that showed impressive impact. If the
results aren't serialized here, maybe that same technique could be used to
further decrease memory consumption.
On another point, I suspect that immutable `CacheEntry` might be easier to
reason about going forward, but maybe that's just me.
> 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)
