Ok let me clarify the steps.
I start Fuseki as a docker container with the config you saw earlier.
Then I load the dataset with curl. After that I intend to use Fuseki as
"read only" query only.
That at moment, there is absolutely no query being done, but still the
memory allocated keeps growing.
> On 2021-07-27, at 19:08:25, Andy Seaborne wrote:
>
>
>
> On 27/07/2021 14:40, Laura Morales wrote:
>> I can actually confirm that this was happening to me as well on a VM with
>> 4GB RAM and TDB store (thus not in-memory). As more and more queries were
>> made, RAM filled up, then the
If the dataset is read-only, then it is always empty. The
fuseki:serviceReadWriteGraphStore is the only way to get data into the
database. The other two services are read-only.
Are you sure it is the database growing and not Java loading classes? On
a tight memory footprint, and because
On Tue, 27 Jul 2021 at 18:04, Andy Seaborne wrote:
>
>
> On 27/07/2021 14:19, Marco Fiocco wrote:
> > Hello,
> >
> > I'm running a in-memory Fuseki 3.16 server and I see that the allocated
> memory keeps growing linearly indefinitely even if idle.
>
> That is strange because if there are no
On 27/07/2021 14:40, Laura Morales wrote:
I can actually confirm that this was happening to me as well on a VM with 4GB
RAM and TDB store (thus not in-memory). As more and more queries were made, RAM
filled up, then the SWAP filled up, and at that point I had to reboot the
machine. My
On 27/07/2021 14:19, Marco Fiocco wrote:
Hello,
I'm running a in-memory Fuseki 3.16 server and I see that the allocated memory
keeps growing linearly indefinitely even if idle.
That is strange because if there are no requests, it does no work.
Initially I reserved 1GB of memory and I've
I can actually confirm that this was happening to me as well on a VM with 4GB
RAM and TDB store (thus not in-memory). As more and more queries were made, RAM
filled up, then the SWAP filled up, and at that point I had to reboot the
machine. My solution was just to restart the server with a
Hello,
I'm running a in-memory Fuseki 3.16 server and I see that the allocated memory
keeps growing linearly indefinitely even if idle.
Initially I reserved 1GB of memory and I've noticed that the process gets OOM
killed every 2 hours. Now I've allocated 2GB because I've read somewhere that
It has N-Quads reader and writer, so write the RdfDataset as N-Quads to
bytes or a string, and parse that. Not ideal at scale but it works;
JSON-LD isn't streaming anyway.
Andy
https://issues.apache.org/jira/browse/JENA-1948
On 27/07/2021 06:25, Philipp Leeb wrote:
Didn't see any way
