On 20/12/13 14:16, Rose Beck wrote:
Ok. Thanks a lot Andy for the link.
Mainly for Maria who has asked the question before
But now from the question ...I am bit curious to understand what is meant
by a running system and time taken to attach a store..in Jena docs. Can you
please clarify?
The store is the database on disk.
Opening it means access the disk so depending on the setup, that can be
distorting on the figures. TDB caches heavily (all databases do - disks
are slow) so it takes time to settle down for meaningful timing figures.
Anyone serious about benchmarks needs to use a framework e.g.
http://www.slideshare.net/RobVesse/practical-sparql-benchmarking
as well as be clear about what exactly they are testing.
The number of academic papers that have weak benchmarks is really quite
alarming. Reviewers are letting through material that does little to
contribute to the literature. Failures include not comparing
like-with-like (e.g memory vs disk, systems that were designed for
something else, ...), and, my pet hate, not running at large enough
scale, so it is running a disk database out of RAM cache.
Useful figures are hard to obtain - not a last minute addition.
Andy
On Fri, Dec 20, 2013 at 7:43 PM, Andy Seaborne <[email protected]> wrote:
On 20/12/13 14:00, Maria Jackson wrote:
Is it possible to find the time that a particular query takes to
run(compilatiion + execution time) in Jena TDB.
I think it is possible add these within the code. But is there any other
way out...is there some build-in Jena TDB feature which allows me to find
the time a query takes in total (i..e plan generation + executing it).
I'll be highly grateful to you for the same.
I have a paper submission deadline tomorrow..an early response is highly
appreciated.
This is a repeat question:
http://mail-archives.apache.org/mod_mbox/jena-users/201311.mbox/%
3CCALZBbQs4PqmX9JXha2EDw3ywRfyFixoJmsZyCMYCFAfYdps3Pw%40mail.gmail.com%3E
store -=
