Java memory will grow to reach about the heap size. This is a java thing
- it does not perform the more expensive forms of garbage collection
until the heap is nearly full. Then it does a more savage GC and the
memory usage will drop (but not the OS process size).
To check - attach a tool such as VisualVM and ask it to force a GC and
see what the memory graph does.
Returning memory to the OS is JEP 346 (for G1 at least) which is in
Java12 (may be experiemntal there)
Andy
On 22/03/2021 10:59, jaa...@kolumbus.fi wrote:
Hello,
I'm running jena-fuseki 3.17.0 in azure cloud with memory-based
datasets. I haven't been updating any data into my datasets for one
week, but I just noticed that the memory consumption still keeps on
increasing (see attachment).
There's another service that queries data from that jena-fuseki-instance
every minute via hypergraphql-interface. Could jena-fuseki somehow cache
those requests causing memory consumption increase ?
If so, is there any means for preventing such caching ?
Br, Jaana
