So, 'set autocommit on" is more efficient than "log_enable(3,1)" ?
This is not the case with me. If I does not "log_enable(3,1)" before the insert/load/delete/clear.., does Virtuoso will use more memory than it is eventually crash. Thanks, Maxime. 2011/9/25 Hugh Williams <[email protected]> > Hi Maxime, > > The difference is that log_enable(3,1) sets row by row autocommit on an > then sets it back off automatically whereas "set autocommit on” sets auto > commit on permanently until explicitly changed, see: > > http://docs.openlinksw.com/virtuoso/fn_log_enable.html > > Best Regards > Hugh Williams > Professional Services > OpenLink Software > Web: http://www.openlinksw.com > Support: http://support.openlinksw.com > Forums: http://boards.openlinksw.com/support > Twitter: http://twitter.com/OpenLink > > On 20 Sep 2011, at 15:13, Maxime Teissèdre wrote: > > Hi, > > "set autocommit on;" and "log_enable(3,1);" are different. > > Now, i run the *log_enable(3,1)* before all requests and the RAM is ok. > > What is the difference between the two commands? > > Thanks, > Maxime T. > > > 2011/8/10 Maxime Teissèdre <[email protected]> > >> Hi, >> >> I have tested the "uniprot graph" (more than 2 billion of triplets) and >> the SWAP isn't used. It's OK for that. >> >> Now, the "LOAD GRAPH" doesn't finish. I don't understand why. >> I'll open an other topic for that. >> >> >> Thanks, >> Maxime T. >> >> > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > > http://p.sf.net/sfu/splunk-d2dcopy1_______________________________________________ > > Virtuoso-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/virtuoso-devel > > >
