Hi Lars,
By default, triple deletion is performed as part of a transaction, which is
stored in memory until the operation is completed and committed to the
database. During typical server operation, deleting one or more graphs
containing a large number of triples (generally millions or more)
* Hugh Williams
Which you will have to perform manually rather than via the Conductor, whose
behaviour will be change to similarly turn of transactions when performing
such operations in the next release ...
Very good answer, thank you. I can work around it for now. Very glad to see
* Hugh Williams
Is this 120K triples already loaded and what is the current triple count of
your Virtuoso instance ?
Yes, they were already loaded. I did some more deletions, and now the total
triple count is 2 295 633. It contains some graphs left over from older work
and some unwanted
I want to try to use Virtuoso for a private web application (non-commercial),
but since this is a virtual host (Linux), it doesn't have much memory available.
Running Virtuoso on my laptop (MacOS X) I see it consistently use 400-600M of
RAM, which is too much for this particular use case. The
Hi Lars,
Is this 120K triples already loaded and what is the current triple count of
your Virtuoso instance ? Assuming an average triple size for v6 of 30bytes *
120K = 3.6 million bytes of memory roughly required for hosting that number of
triples. Thus what else is being hosted/run on your
