Re: Heap space problem with insert where

Thanks a lot for the explanations! Harri On 24.9.2021 12.15, Andy Seaborne wrote: Inline... On 24/09/2021 09:13, Harri Kiiskinen wrote: Hi all, and thanks for the support! I did manage to resolve the problem by modifying the query, detailed comments below. Harri K. On 23.9.2021 22.47,

Re: Heap space problem with insert where

sure and if its fits your your use case even better On Fri, Sep 24, 2021 at 9:41 AM Harri Kiiskinen wrote: > Perhaps so; but as a tool, Jena, and SPARQL in general, is very suitable > for managing and processing data so that the processes can be described > and repeated. For example in this

Re: Heap space problem with insert where

Inline... On 24/09/2021 09:13, Harri Kiiskinen wrote: Hi all, and thanks for the support! I did manage to resolve the problem by modifying the query, detailed comments below. Harri K. On 23.9.2021 22.47, Andy Seaborne wrote: I guess you are using TDB2 if you have -Xmx2G. TDB1 wil use even

Re: Heap space problem with insert where

Perhaps so; but as a tool, Jena, and SPARQL in general, is very suitable for managing and processing data so that the processes can be described and repeated. For example in this case, processing the results of the OCR is very quick compared to the actual OCR process, so I prefer to store the

Re: Heap space problem with insert where

All that said, I would think you'd be best advised to run this type of operation outside of Jena during preprocessing with CLI tools such as grep, sed, awk or ack. On Fri, Sep 24, 2021 at 9:14 AM Harri Kiiskinen wrote: > Hi all, > > and thanks for the support! I did manage to resolve the

Re: Heap space problem with insert where

Hi all, and thanks for the support! I did manage to resolve the problem by modifying the query, detailed comments below. Harri K. On 23.9.2021 22.47, Andy Seaborne wrote: I guess you are using TDB2 if you have -Xmx2G. TDB1 wil use even more heap space. Yes, TDB2. All those named

Re: Heap space problem with insert where

Hi Harri, I guess you are using TDB2 if you have -Xmx2G. TDB1 wil use even more heap space. All those named variables mean that the intermediate results are being held onto. That includes the "no change" case. It looks like REPLACE and no change is still a new string. There is at least 8

Re: Heap space problem with insert where

"not to bind" to be read as "just bind once" On Thu, Sep 23, 2021 at 4:25 PM Marco Neumann wrote: > set -Xmx to 8G and try not to bind the variable and to see if this > alleviates the issue. > > On Thu, Sep 23, 2021 at 12:41 PM Harri Kiiskinen > wrote: > >> Hi! >> >> I'm trying to run a simple

Re: Heap space problem with insert where

set -Xmx to 8G and try not to bind the variable and to see if this alleviates the issue. On Thu, Sep 23, 2021 at 12:41 PM Harri Kiiskinen wrote: > Hi! > > I'm trying to run a simple update query that reads strings from one graph, > processes them, and stores to another: > > >

Heap space problem with insert where

Hi! I'm trying to run a simple update query that reads strings from one graph, processes them, and stores to another: -- insert { graph vice:pageocrdata_clean { ?page vice:ocrtext ?ocr7 . } } where {