Re: Fuseki 0.2.3 performance / StatsMatcher warnings

[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:fileMode=direct --loc=... '...query...'

        Andy

I have checked that the DB isn't being reopened each time - it's open
once on start up and not within a run.

     Andy

Regards,

Michael Brunnbauer