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) can consume available memory to the point where the operation cannot be completed, and thus the graph(s) cannot be deleted. Such large graphs can be cleared by changing the transaction log mode to autocommit on each operation, deleting the graph(s) or triples, and then setting the log mode back to its original setting. This can done using the Virtuoso log_enable function, with the settings log_enable(3,1) as detailed at:
http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtTipsAndTricksGuideDeleteLargeGraphs
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 ...
Best Regards
Hugh Williams
Professional Services
OpenLink Software, Inc. // http://www.openlinksw.com/
10 Burlington Mall Road, Suite 265, Burlington MA 01803
Weblog -- http://www.openlinksw.com/blogs/
LinkedIn -- http://www.linkedin.com/company/openlink-software/
Twitter -- http://twitter.com/OpenLink
Google+ -- http://plus.google.com/100570109519069333827/
Facebook -- http://www.facebook.com/OpenLinkSoftware
Universal Data Access, Integration, and Management Technology Providers
On 24 Feb 2012, at 12:04, Lars Marius Garshol wrote:
>
> * 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 graphs pulled in by Virtuoso (presumably by spongers).
>
> It seems I've made a mistake, because now Virtuoso uses 161M on startup. Even
> if I start running queries and using it for real it stays at that memory
> usage.
>
> However, if I try to delete some more of the unwanted graphs (via the graphs
> display in Conductor) memory usage rapidly increases into the 450M range. The
> biggest graph has 1 751 330 statements, and trying to delete this graph
> causes an error:
>
> 40005SR325: Transaction aborted because it's log after image size went above
> the limit in v:vscx "navbar1" (render)
>
> I think the memory usage issues I saw earlier were somehow related to this.
> I'm not sure why memory usage increased on startup, too, but it might have
> something to do with having 4-5 aborted transactions of this type in the log
> when starting up.
>
> Not being able to delete graphs looks worrying, though. Any ideas about
> what's causing this?
>
>> So you should be able to get it to run within 200MB ...
>
> It does seem like I should, yes. Thanks for the tips in your email. They may
> come in handy at other times.
>
> Thanks a lot for the help!
>
> --Lars M.
> http://www.garshol.priv.no/tmphoto/
> http://www.garshol.priv.no/blog/
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Virtuoso-users mailing list
> Virtuoso-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
smime.p7s
Description: S/MIME cryptographic signature
