So, as a comparison this is the jconsole overview when using defaultGraph instead of namedGraph https://lut.im/5gKUNX0MdF/iRpiXLfTtDNapAIU.png The CPU spike at the start of the graph is when I issued the query, which returned before the CPU graph returns to zero. Unfortunately jconsole seems to sample data every few seconds, so I think the graph is not very accurate because the query returned more quickly than jconsole is sampling. But it's good enough to see the difference with the previous graph.
- Re: Very very slow query when using a high OFFSET Laura Morales
- Re: Very very slow query when using a high OFFSET Lorenz Buehmann
- Re: Very very slow query when using a high OFFSET Laura Morales
- Re: Very very slow query when using a high OFFSET Lorenz Buehmann
- Re: Very very slow query when using a high OFFSET Andy Seaborne
- Re: Very very slow query when using a high OFFSET Laura Morales
- Re: Very very slow query when using a high OFFSET Andy Seaborne
- Re: Very very slow query when using a high OFFSET Laura Morales
- Re: Very very slow query when using a high OFFSET Andy Seaborne
- Re: Very very slow query when using a high OFFSET Laura Morales
- Re: Very very slow query when using a high OFFSET Laura Morales
- Re: Very very slow query when using a high OFFSET dandh988
- Re: Very very slow query when using a high OFFSET Laura Morales
- Re: Very very slow query when using a high OFFSET dandh988
- Re: Very very slow query when using a high OFFSET Laura Morales
- Re: Very very slow query when using a high OFFSET James Anderson
- Re: Very very slow query when using a high OFFSET Lorenz Buehmann
- Re: Very very slow query when using a high OFFSET Laura Morales
- Re: Very very slow query when using a high OFFSET Andy Seaborne
- Re: Very very slow query when using a high OFFSET Laura Morales
- Re: Very very slow query when using a high OFFSET dandh988