There has been some interest in this mailing list on RDF DB comparisons.
Below is part of my write-up of preliminary results found while building
a DB Shootout suite. I will appreciate any comments.
Vineet
----------------
In building applications to allow end-users to manage information in an
intuitive manner (from multiple sources), we, the Haystack and Simile
projects, have over time moved to using the W3C's Semantic Web framework
and RDF standard for sharing data and using as application's backends.
Using RDF does require us to either build or find an easily deployable
and high-performance data-store, and we have therefore planned an
in-depth 'RDF DB Shootout'. Preliminary results indicate that the Sesame
Native store to have the best performance.
Our preliminary evaluation consisted of using the Java API’s against
available Java RDF-API’s. We considered: the Jena 2.2 API with Apache
Derby and Berkley DB backends, the Sesame 1.2.2 Native Store, and
Haystack’s Cholestrol 4 DB. We also tried using the Redland API’s,
however, we had difficulties in getting it built with Java API’s on Windows.
*Results*: Sesame’s Native store added data roughly 20x faster and
performed lookups at roughly 2.5x faster than any of Jena’s backends.
When compared to Sesame, Cholesterol ran 50% slower in data-addition
while it ran 50% faster in the lookups.
More Details (including the description of the suite, the actual
numbers, and limitations of the results) at:
http://vineet.i3labs.org/wp/2006/01/08/rdf-db-shootout-preliminary-results/
Received on Sun Jan 08 2006 - 08:56:06 EST