Hello Andy, On Thu, Jul 12, 2012 at 02:46:49PM +0100, Andy Seaborne wrote: > The things to try that occur to be are to simplify the situation: > > 1/ Run with only one dataset on the server
Does not help. > 2/ Change the workload: do multiple calls of each query , so do > q1,q1,q1,q1,q2,q2,q2,q2, etc Immediately repeating a query does not make it fast. I now have a set of queries which is slow against the dbpedia dataset (156966301 quads) and very fast against the ontology dataset (12177 quads). There are results for some of the queries in both datasets. Queries that return no results do not seem to be faster. There is no significant disk activity while I run the queries (the machine has 48GB RAM and everything relevant is in memory after the first time I run the queries). I can see that Fuseki is under high cpu load (99%) while I run the queries. Fuseki has a virtual size high above 4GB - so it seems to use memory mapped IO for the TDB files. Regards, Michael Brunnbauer -- ++ Michael Brunnbauer ++ netEstate GmbH ++ Geisenhausener Straße 11a ++ 81379 München ++ Tel +49 89 32 19 77 80 ++ Fax +49 89 32 19 77 89 ++ E-Mail [email protected] ++ http://www.netestate.de/ ++ ++ Sitz: München, HRB Nr.142452 (Handelsregister B München) ++ USt-IdNr. DE221033342 ++ Geschäftsführer: Michael Brunnbauer, Franz Brunnbauer ++ Prokurist: Dipl. Kfm. (Univ.) Markus Hendel
