On Feb 6, 2017, at 12:20 PM, Davis, Daniel (NIH/NLM) [C] <daniel.da...@nih.gov> wrote: > > So, I have virtuoso, and I spend some time loading lots of ntriples files > into it with TTLP, and then I wait for 2 minutes for checkpoint to complete, > with CheckpointInterval = 60. Then, I restart it with +wait. It still > has lots of I/O to do, doing a roll forward. > > The Database Administration section, > http://docs.openlinksw.com/virtuoso/dbadm/, does not define the units for > checkpoint interval – can I assume that I would have needed to wait 60 > minutes to assure that a checkpoint had been taken and no roll-forward would > be necessary? > > If not, can someone please explain what I can do to assure that I/O needed is > done in a timely fashion. I used to have the following in my load code, but > I took it out to avoid a crash that may or may not have been related: > > Checkpoint_interval(-1); > CHECKPOINT; > Checkpoint_interval(60); > > Thanks, > > Dan Davis, Systems/Applications Architect (Contractor), > Office of Computer and Communications Systems, > National Library of Medicine, NIH
Hi, Dan -- The unit of checkpointinterval is minutes, as should be stated everywhere this setting is discussed, and as I've just confirmed is stated here -- • http://docs.openlinksw.com/virtuoso/fn_checkpoint_interval/ • http://docs.openlinksw.com/virtuoso/dbadm/#ini_parameters_checkpointinterval Units are not currently indicated in the INI file; we'll be adding a comment for this, but that will not necessarily persist through changes to that file, as many use actions can strip comments. (If you have specific pointers to somewhere these units are not mentioned, other than the sample INI in the page you linked, I'll make sure those get updated.) I'm not sure what you were trying to achieve with these three lines, especially if they were run as shown, without any other calls between -- > Checkpoint_interval(-1); > CHECKPOINT; > Checkpoint_interval(60); Note that you do not need to change the automatic interval in order to run a manual checkpoint. Presuming the starting state was that the interval was its default (i.e., 60), you could replace the three lines above with the single -- > CHECKPOINT; When a checkpoint is run, the transaction file should be purged. If you immediately shut down the instance, there should thus be no (or a zero-byte) .trx file, and thus no roll-forward to wait through on next launch. I hope this information is helpful. Regards, Ted -- A: Yes. http://www.idallen.com/topposting.html | Q: Are you sure? | | A: Because it reverses the logical flow of conversation. | | | Q: Why is top posting frowned upon? Ted Thibodeau, Jr. // voice +1-781-273-0900 x32 Senior Support & Evangelism // mailto:tthibod...@openlinksw.com // http://twitter.com/TallTed 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
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________ Virtuoso-users mailing list Virtuoso-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtuoso-users
