Since this thread has got complex, I'm posting this update here at the
top level.
Thanks to folks, especially Andy and Rob for suggestions and for
investigating.
After a lot more testing at our end I believe we now have some workarounds.
First, at least on java 17, the process growth does
On 10/07/2023 12:18, Andy Seaborne wrote:
Laura, Dave,
This doesn't sound like the same issue but let's see.
Sorry for the confusion - these questions are for Laura.
- Is it in a container? If so:
Is it the container being killed OOM or
Java throwing an OOM exception?
Much
Hi Andy,
On 10/07/2023 12:18, Andy Seaborne wrote:
Laura, Dave,
This doesn't sound like the same issue but let's see.
It may well be different, if so apologies for causing noise.
Dave - your situation isn't under high load is it?
We see the process size growth under no load other than
Hi Rob,
On 10/07/2023 14:05, Rob @ DNR wrote:
Dave
Poked around a bit today but not sure I’ve reproduced anything as such or found
any smoking guns
I ran a Fuseki instance with the same watch command you showed in your last
message. JVM Heap stays essentially static even after hours,
Dave
Poked around a bit today but not sure I’ve reproduced anything as such or found
any smoking guns
I ran a Fuseki instance with the same watch command you showed in your last
message. JVM Heap stays essentially static even after hours, there’s some
minor fluctuation up and down in used
Laura, Dave,
This doesn't sound like the same issue but let's see.
Dave - your situation isn't under high load is it?
- Is it in a container? If so:
Is it the container being killed OOM or
Java throwing an OOM exception?
Much RAM does the container get? How many threads?
- If not a
While we appreciate that this unresolved memory issue is painful for users, I
would strongly emphasise that the project DOES NOT recommend people use
outdated versions of Jena.
3.17.0 released in November 2020 which makes it 2.5 years old at this point.
There have been lots of security,
There is an issue with memory growth in fuseki, though it's growth
outside of normal java heap and non-heap space.
See https://www.mail-archive.com/users@jena.apache.org/msg20362.html
For that scale of data and scale of machine suggest setting the heap
smaller -Xmx1G or -Xmx500M. Empirically
