Comments on: Billions and billions… http://clarkparsia.com/weblog/2006/02/20/billions-and-billions/ Make lots of money through stealth in shadows Wed, 07 Jan 2009 01:22:01 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Arjohn http://clarkparsia.com/weblog/2006/02/20/billions-and-billions/comment-page-1/#comment-51 Arjohn Wed, 22 Feb 2006 12:04:09 +0000 http://clarkparsia.com/weblog/?p=28#comment-51 Based on the white paper, I would say this is an impressive piece of work. The white paper is a bit low on details though, and leaves me with many questions. Does the reported storage time include any inferencing? Did they use full ACID compliant transaction (apparently, this is optional)? Considering that the Lehigh University Benchmark was used for scalability testing, what are the results of the queries included with this benchmark? Further, the reported 4000 triples/sec for data sets larger than 200M seems a bit arbitrary. This figure will likely go down as data sets grow. Also, performance depends on lots of factors, including the specifics of the data set that was used (see also: <a href="http://jeenbroekstra.blogspot.com/2006/02/pitfalls-in-benchmarking-triple-stores.html" rel="nofollow">Pitfalls in Benchmarking Triple Stores</a>). The low-level API that is mentioned surprises me a bit: it doesn't include any operations for removing triples! Does this mean that you can't remove anything from their database? Anyway, interesting read but it lacks a lot of details. Dr. Dobbs probably constrains the length of the article too much to be able to include such details. <a href="http://www.franz.com/products/allegrocache/AllegroCache_White_Paper.pdf" rel="nofollow">This white paper</a> gives some more info on the non-RDF parts of AllegroCache. Based on the white paper, I would say this is an impressive piece of work. The white paper is a bit low on details though, and leaves me with many questions. Does the reported storage time include any inferencing? Did they use full ACID compliant transaction (apparently, this is optional)? Considering that the Lehigh University Benchmark was used for scalability testing, what are the results of the queries included with this benchmark?

Further, the reported 4000 triples/sec for data sets larger than 200M seems a bit arbitrary. This figure will likely go down as data sets grow. Also, performance depends on lots of factors, including the specifics of the data set that was used (see also: Pitfalls in Benchmarking Triple Stores).

The low-level API that is mentioned surprises me a bit: it doesn’t include any operations for removing triples! Does this mean that you can’t remove anything from their database?

Anyway, interesting read but it lacks a lot of details. Dr. Dobbs probably constrains the length of the article too much to be able to include such details. This white paper gives some more info on the non-RDF parts of AllegroCache.

]]> By: Arjohn http://clarkparsia.com/weblog/2006/02/20/billions-and-billions/comment-page-1/#comment-8281 Arjohn Wed, 22 Feb 2006 09:04:09 +0000 http://clarkparsia.com/weblog/?p=28#comment-8281 Based on the white paper, I would say this is an impressive piece of work. The white paper is a bit low on details though, and leaves me with many questions. Does the reported storage time include any inferencing? Did they use full ACID compliant transaction (apparently, this is optional)? Considering that the Lehigh University Benchmark was used for scalability testing, what are the results of the queries included with this benchmark?<br><br>Further, the reported 4000 triples/sec for data sets larger than 200M seems a bit arbitrary. This figure will likely go down as data sets grow. Also, performance depends on lots of factors, including the specifics of the data set that was used (see also: <a href="http://jeenbroekstra.blogspot.com/2006/02/pitfalls-in-benchmarking-triple-stores.html" rel="nofollow">Pitfalls in Benchmarking Triple Stores</a>).<br><br>The low-level API that is mentioned surprises me a bit: it doesn't include any operations for removing triples! Does this mean that you can't remove anything from their database?<br><br>Anyway, interesting read but it lacks a lot of details. Dr. Dobbs probably constrains the length of the article too much to be able to include such details. <a href="http://www.franz.com/products/allegrocache/AllegroCache_White_Paper.pdf" rel="nofollow">This white paper</a> gives some more info on the non-RDF parts of AllegroCache. Based on the white paper, I would say this is an impressive piece of work. The white paper is a bit low on details though, and leaves me with many questions. Does the reported storage time include any inferencing? Did they use full ACID compliant transaction (apparently, this is optional)? Considering that the Lehigh University Benchmark was used for scalability testing, what are the results of the queries included with this benchmark?

Further, the reported 4000 triples/sec for data sets larger than 200M seems a bit arbitrary. This figure will likely go down as data sets grow. Also, performance depends on lots of factors, including the specifics of the data set that was used (see also: Pitfalls in Benchmarking Triple Stores).

The low-level API that is mentioned surprises me a bit: it doesn’t include any operations for removing triples! Does this mean that you can’t remove anything from their database?

Anyway, interesting read but it lacks a lot of details. Dr. Dobbs probably constrains the length of the article too much to be able to include such details. This white paper gives some more info on the non-RDF parts of AllegroCache.

]]>