Jörn, > On 23 Nov 2015, at 01:46, Jörn Hees <j_h...@cs.uni-kl.de> wrote: > > Hi Hugh, > > thanks again for your replies... > >> On 22 Nov 2015, at 01:46, Hugh Williams <hwilli...@openlinksw.com> wrote: >> >>> What puzzles me is that after import and several checkpoints and restarts, >>> just leaving the DB idle without any queries (see below) it seems to become >>> busy. >>> I guess it does some kind of "re-organization" and i'd mostly like to find >>> out how i can tell it "do it now, take all resources you want, don't care >>> if anyone is waiting, admin override, full speed ;)". >>> That would allow me to then have that static state of the DB which i can >>> back-up and replay if things go wrong or someone wants an old version, >>> leaving us with "ready to use" backups, and not such that first start some >>> lengthy "re-organization after mass import". >>> >>> The mentioned "re-organization state" now seems to be over after leaving >>> the DB switched on and idle for the last couple of days. >> >> [Hugh] Does your database have Full Text indexing enabled which would is a >> scheduled background task that would take time to complete on a newly loaded >> large database like yours, see: >> >> >> http://docs.openlinksw.com/virtuoso/sparqlextensions.html#rdfsparqlrulefulltext > > I really think that this could be it, as by default there seems to be an > "all" index.
[Hugh] If you installed the Virtuoso Faceted Browser then the FT index would be enabled and run as a scheduled job. > > Reading the doc page, i have two remaining questions: > > After a normal `rdf_loader_run()`, would a > `DB.DBA.VT_INC_INDEX_DB_DBA_RDF_OBJ();` be sufficient to get a complete > full-text index? Or do i have to run `DB.DBA.RDF_OBJ_FT_RECOVER();` in those > cases and will otherwise never arrive at a complete free-text index (not even > after the background tasks finished?)? [Hugh] The scheduler will run `DB.DBA.VT_INC_INDEX_DB_DBA_RDF_OBJ();` so you can wait for it to run or run it manually itself. > If i have to, a mention of this around > http://docs.openlinksw.com/virtuoso/rdfperformancetuning.html#rdfperfloadinglod > would be nice. > > I ran `DB.DBA.RDF_OBJ_FT_RECOVER();` on a small instance with just the > DBpedia core (~ 430 M triples) and it seems to only use 2 - 3 CPUs with very > little IO. The whole importing of that dataset only took 1:30 hours, but the > full-text indexing is still running after 3 hours now... Is there any way to > go full speed at the cost of locking the whole DB or something? [Hugh] Will have to check with development as I am not aware of a param to control CPU usage, it should run with full platform utilisation I would have thought … Regards Hugh > > Cheers, > Jörn > > > ------------------------------------------------------------------------------ Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140 _______________________________________________ Virtuoso-users mailing list Virtuoso-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtuoso-users