View source for LargeTripleStores

__NOTOC__
This page is for references to signed quotes of deployments of large triples stores rather than predictions of what some software might scale to. 

== Kowari (10-20M, then 160M) ==
"My own testing has been in the 10-20M triple range."
-- [http://lists.w3.org/Archives/Public/semantic-web/2005Sep/0027.html Chris Wilper]

''Addendum from Chris on Nov 7th, 2005:'' Since this was written, we have successfully loaded over 160M triples into Kowari on a 64-bit machine with 6GB physical memory.  A 64-bit machine is really required to bring Kowari up to this level because it uses mapped files and needs a lot of address space.  In our experience in this environment, simple queries still perform fairly well (a few seconds) and complex queries involving 8-10 triple patterns perform worse (a few minutes to an hour).

== Sesame (10-20M) ==

(10-20 million triples) " is a lot, but most serious triple stores can handle this I'd say. 
Sesame certainly can, ..."
-- [http://lists.w3.org/Archives/Public/semantic-web/2005Sep/0029.html Jeen Broekstra, Aduna]

== 3store with MySQL 3 (100M) ==
"The store my consortium produces (3store) is used successfully up to
100M triples or so. Beyond that it gets a bit sketchy. I'm currently
looking at ways to make it scale to 10^9+ without specialising the store
to a particular schema."

More specifically, one user is running it with 120M triples in MySQL 4.1. At that size query works fine, but assertion time is down to about 300 triples/second, which makes growing it any bigger too painful. I should note that 3store is an RDFS store, in version 3 it's possible to disable the inference, which should make it scale to much larger sizes, but there are plenty of other stores that can run vanilla RDF storage well.
-- [http://lists.w3.org/Archives/Public/semantic-web/2005Sep/0030.html Steve Harris, AKT]

== RDF gateway (262M) ==
"the [http://www.isb-sib.ch/~ejain/uniprot-rdf/data/ UniProt protein database] (262 million triples) and RDF Gateway."
-- [http://lists.w3.org/Archives/Public/semantic-web/2005Sep/0031.html Geoff Chappell, Intellidimension]

== Jena with PostgreSQL (200M) ==
"Our store is pretty big -- its about 200M triples.

We're currently using Jena on Postgres. For our needs this worked out
better than Jena/MySQL, Sesame, and Kowari."
-- [http://lists.w3.org/Archives/Public/semantic-web/2005Sep/0038.html Leigh Dodds, Ingenta]

= Questions =

I know storing 200M triples is cool. But which store can handle simultaneous queries of about 10.000 users using RDFS inferencing? -- Anonymous

200M or so seems to be about the max that anybody has reported. It would be very helpful if people could state whether they tried to scale further, and if not able to, what the problems were &mdash; i.e., does it become too slow to add, trivial queries, complex queries, etc. Also, it would be extremely helpful if hardware specs were included. -- CS 

= Related =

* [[LargeQuadStores]] (or Named Graphs or Context) but many of the above do these too
* [[TripleStoreScalability]]