Even if you turn on full "explain" logging (if Fuseki can do that), it
probably won't help you much - it's very much about the internals of ARQ
and tells what is happening, not why it is happening.
Instead, think about the query - break it in parts and see how much each
part costs.
Maybe look at the output of "qparse --print=opt" This is meaningful when
combined with knowledge of the optimizer and the meaning of the algebra
operations.
Andy
On 23/05/17 14:13, [email protected] wrote:
Those settings are going to give you fairly sparse logging data. You may
need to "turn it up" a bit. According to:
https://jena.apache.org/documentation/query/explain.html#execution-logging
you could turn on the logger
log4j.logger.org.apache.jena.arq.exec=INFO
ajs6f
Laura Morales wrote on 5/23/17 8:13 AM:
Look in the Fuseki log file.
Thanks I can see the query and execution time. However I only have a
single "run/logs/stderrout.log" is this how it's supposed to look like?
I've also tried creating the file log4j.properties using these
settings
https://github.com/apache/jena/blob/master/jena-fuseki2/jena-fuseki-core/src/main/resources/org/apache/jena/fuseki/log4j.properties
but doesn't seem to make much of a difference...
