https://ontologforum.com/index.php?action=history&feed=atom&title=OntologySummit2014_Hackathon_ReferenceDataForSPARQLPeformanceBenchmarking 2026-06-28T08:55:47Z Revision history for this page on the wiki MediaWiki 1.39.0 https://ontologforum.com/index.php?title=OntologySummit2014_Hackathon_ReferenceDataForSPARQLPeformanceBenchmarking&diff=2758&oldid=prev 2014-04-28T02:59:11Z

<p>Last updated at: 2014-03-19 04:23:08 By user: VictorChernov</p> <p><b>New page</b></p><div>= [[OntologySummit2014_Hackathon]] - Project: =<br /> <br /> == Optimized SPARQL performance management via native API ==<br /> <br /> Project roster page: [[OntologySummit2014_Hackathon_ReferenceDataForSPARQLPeformanceBenchmarking]] (this page). <br /> <br /> Team lead: [[VictorChernov]] (MSK, UTC+4) vchernov at nitrosbase.com <br /> <br /> Event starts 29th of March 2014 14:00 MSK / 10:00 UTC / 03:00 PST all over the world via mikogo.com (the session # will come later) <br /> <br /> ----<br /> <br /> The Goals of the project are <br /> <br /> Studying the kinds of queries revealing the advantages of one or another RDF database. The goals imply: <br /> <br /> * Selection of a SPARQL subset from SP2Bench <br /> * Formin a dataset and loading it to all triple-stores. <br /> * Implementing measurement aids, testing <br /> * Accurate time measurement, getting min, max, average and median times. <br /> * Reflection on the results, advantages and disadvantages of the triplestores on each selected query. <br /> <br /> The following triplestores will be compared: <br /> <br /> * [http://virtuoso.openlinksw.com/ Virtuoso] <br /> * [http://stardog.com/ Stardog] <br /> * [http://nitrosbase.com/ [[NitrosBase]]] <br /> <br /> The triplestores have the following important advantages: <br /> <br /> * Very high performance on demonstrated on sp2bench benchmark <br /> * Linux and Windows versions <br /> * Native API for fast query processing <br /> <br /> It is important to use native API for fast query execution. All 3 tools provide native API: <br /> <br /> ; Virtuoso : Jena, Sesame and Virtuoso ODBC RDF Extensions for SPASQL <br /> ; Stardog : the core SNARL (Stardog Native API for the RDF Language) classes and interfaces <br /> ; [[NitrosBase]] : C++ and .NET native API <br /> <br /> We suppose writing additional codes needed for accurate testing: <br /> <br /> * Accurate time measurement; <br /> * Functions for getting min, max, average and median times; <br /> * Functions for getting time of scanning through the whole query result; <br /> * Functions for getting time of retrieving first several records (for example, the first page of web grid); <br /> * Etc. <br /> <br /> The following steps are needed for loading test dataset: <br /> <br /> * Selecting a data subset from sp2bench benchmark <br /> * Measuring data loading time <br /> <br /> '''''Note:'''''<br /> ''Data are considered as loaded as soon as the system is ready to perform a simplest search query. This is done to eliminate background processes (eg. indexing).'' <br /> <br /> We are going to explore the query execution performance by the databases under consideration (Virtuoso, Stardog, [[NitrosBase]]). <br /> <br /> The queries should be fairly simple and cover the different techniques, for example: <br /> <br /> * search the small range of values <br /> * search the big range of values <br /> * Sorting <br /> * Aggregation <br /> * Several different join queries <br /> * Retrieving part of result <br /> * Retrieving whole result <br /> * etc. <br /> <br /> '''''Note:'''''<br /> ''During testing each database may allocate a lot of resources, that can affect the performance of other databases. That’s why each test should be stared from system reboot.''</div>

imported>Admin