Re: Fuseki 0.2.3 performance / StatsMatcher warnings

2012-08-05 Thread Andy Seaborne
On 05/08/12 12:03, Michael Brunnbauer wrote: Hello Andy, much better now. Thank you very much :-) Good! I guess it's OK to rename stats.opt to stats.opt.old instead of moving it out of the directory ? Yes - it's the specific name "stats.opt" that the code looks for. Andy Rega

Re: Fuseki 0.2.3 performance / StatsMatcher warnings

2012-08-05 Thread Michael Brunnbauer
Hello Andy, much better now. Thank you very much :-) I guess it's OK to rename stats.opt to stats.opt.old instead of moving it out of the directory ? Regards, Michael Brunnbauer On Sat, Aug 04, 2012 at 05:49:41PM +0100, Andy Seaborne wrote: > Hi Michael. > > (Michael has sent me a copy of th

Re: Fuseki 0.2.3 performance / StatsMatcher warnings

2012-08-04 Thread Andy Seaborne
Hi Michael. (Michael has sent me a copy of this database he's using - a bit big too email even though it's only 157,809,969 triples and 44Gbytes). I can recreate this - I'm getting a total of 5006ms for the query set of 17 queries you're using. With a fix, it's 150ms made up of approx 50ms

Re: Fuseki 0.2.3 performance / StatsMatcher warnings

2012-07-18 Thread Michael Brunnbauer
Hello Andy, On Sun, Jul 15, 2012 at 08:21:50PM +0100, Andy Seaborne wrote: >sparql-wrapper can be eliminated by running >wget -O /dev/null 'http://ts.foaf-search.net:3030/foaf/query?query=' This does not make a difference. > >Running in direct mode (-Dtdb:fileMode=direct and an info levelk

Re: Fuseki 0.2.3 performance / StatsMatcher warnings

2012-07-15 Thread Andy Seaborne
Running in direct mode (-Dtdb:fileMode=direct and an info levelk logging event happens) would see if it's some weird mmap issue to do with the different Jetty's. also, running against the dataset not in Fuseki would eliminate Fuseki-isms: tdbquery --loc=... '...query...' tdbquery --set tdb:file

Re: Fuseki 0.2.3 performance / StatsMatcher warnings

2012-07-15 Thread Andy Seaborne
On 13/07/12 11:33, Michael Brunnbauer wrote: 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

Re: Fuseki 0.2.3 performance / StatsMatcher warnings

2012-07-13 Thread Michael Brunnbauer
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

Re: Fuseki 0.2.3 performance / StatsMatcher warnings

2012-07-13 Thread Andy Seaborne
> For 10K transactions, 3.2s; for 10K transactions and simple query 5.7s. Now 1.1s and 3.457s for 10k actions of which the JIT and misc setup is significant because running x10 N = 100k => Time = 4.242 for what was the 1.1s case. So that's faster (removing a bunch of unnecessary OS system ca

Re: Fuseki 0.2.3 performance / StatsMatcher warnings

2012-07-12 Thread Andy Seaborne
On 12/07/12 10:14, Andy Seaborne wrote: On 11/07/12 20:57, Michael Brunnbauer wrote: but it could be the transaction overhead +1 Not that simple ... another prime candidate is not managing connections in the same way e.g. connection caching as is managing the dataset with open/close. These

Re: Fuseki 0.2.3 performance / StatsMatcher warnings

2012-07-12 Thread Andy Seaborne
On 11/07/12 20:57, Michael Brunnbauer wrote: but it could be the transaction overhead +1 Not that simple ... another prime candidate is not managing connections in the same way e.g. connection caching as is managing the dataset with open/close. These are Fuseki things. The TDB transactio

Re: Fuseki 0.2.3 performance / StatsMatcher warnings

2012-07-11 Thread Michael Brunnbauer
Hello Andy, On Wed, Jul 11, 2012 at 08:18:53PM +0100, Andy Seaborne wrote: > Could you try: > > 1/ SELECT (count(*) AS ?count) WHERE ... >and let me know the counts. 6 2 0 0 0 ... > 2/ SELECT (count(DISTINCT *) AS ?count) WHERE ... >and let me know the counts. 6 2 0 0 0 ... > 3/ Chan

Re: Fuseki 0.2.3 performance / StatsMatcher warnings

2012-07-11 Thread Andy Seaborne
On 11/07/12 19:59, Michael Brunnbauer wrote: Hello Andy, On Wed, Jul 11, 2012 at 07:04:21PM +0100, Andy Seaborne wrote: I have just replaced Joseki 3.4.3 with Fuseki 0.2.3 for our projects www.foaf-search.net and www.semantic-search.info. Which version of TDB are you using with Joseki? I wa

Re: Fuseki 0.2.3 performance / StatsMatcher warnings

2012-07-11 Thread Michael Brunnbauer
Hello Andy, On Wed, Jul 11, 2012 at 07:04:21PM +0100, Andy Seaborne wrote: > >I have just replaced Joseki 3.4.3 with Fuseki 0.2.3 for our projects > >www.foaf-search.net and www.semantic-search.info. > Which version of TDB are you using with Joseki? I was using the Joseki-3.4.3 distribution whic

Re: Fuseki 0.2.3 performance / StatsMatcher warnings

2012-07-11 Thread Andy Seaborne
On 11/07/12 16:05, Michael Brunnbauer wrote: hi all I have just replaced Joseki 3.4.3 with Fuseki 0.2.3 for our projects www.foaf-search.net and www.semantic-search.info. Which version of TDB are you using with Joseki? I have used config-tdb.ttl as starting point for the configuration. My f

Fuseki 0.2.3 performance / StatsMatcher warnings

2012-07-11 Thread Michael Brunnbauer
hi all I have just replaced Joseki 3.4.3 with Fuseki 0.2.3 for our projects www.foaf-search.net and www.semantic-search.info. I have used config-tdb.ttl as starting point for the configuration. My first impression is that it is *much* slower. Is this normal ? More configuration details on demand.