OntologySummit2014_Hackathon - Project:    (4A27)

Optimized SPARQL performance management via native API    (4A2A)

Project roster page: OntologySummit2014_Hackathon_ReferenceDataForSPARQLPeformanceBenchmarking (this page).    (4A25)

Team lead: VictorChernov (MSK, UTC+4) vchernov at nitrosbase.com    (4A29)

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)    (4A57)

The Goals of the project are    (4A2C)

Studying the kinds of queries revealing the advantages of one or another RDF database. The goals imply:    (4A2D)

The following triplestores will be compared:    (4A2J)

The triplestores have the following important advantages:    (4A2N)

It is important to use native API for fast query execution. All 3 tools provide native API:    (4A2S)

Virtuoso    (4A2T)
Jena, Sesame and Virtuoso ODBC RDF Extensions for SPASQL    (4A2U)
Stardog    (4A2V)
the core SNARL (Stardog Native API for the RDF Language) classes and interfaces    (4A2W)
NitrosBase    (4A2X)
C++ and .NET native API    (4A2R)

We suppose writing additional codes needed for accurate testing:    (4A2Y)

The following steps are needed for loading test dataset:    (4A34)

Note: 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).    (4A36)

We are going to explore the query execution performance by the databases under consideration (Virtuoso, Stardog, NitrosBase).    (4A38)

The queries should be fairly simple and cover the different techniques, for example:    (4A39)

Note: 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.    (4A3J)