[
https://issues.apache.org/jira/browse/JENA-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249370#comment-15249370
]
ASF GitHub Bot commented on JENA-626:
-------------------------------------
Github user osma commented on the pull request:
https://github.com/apache/jena/pull/95#issuecomment-212280436
FWIW, I'm in favour of storing the result set before serialization, instead
of caching the serialized results as is apparently currently done. It makes
technical sense, for the reasons @afs mentioned. I don't care if it's slightly
slower than Varnish - if I want the extreme speed, I can always use Varnish as
an additional layer.
From a server administrator perspective, I'd prefer having some sort of
control over the cache size, preferably in terms of bytes rather than number of
items. Currently I have no idea how much this cache will affect Fuseki memory
usage. If it's, say, below 100MB currently, then I don't care that much, but if
it can get into the gigabyte range (for example with many large result sets),
then it's going to affect server performance and I'd perhaps rather allocate
that memory to Varnish (which can also store compressed responses, so the same
memory can fit many more objects).
> 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)
