DISQUS

DISQUS Hello! Thinking Clearly is using DISQUS, a powerful comment system, to manage its comments. Learn more.

Community Page

  • Subscribe

  • Community

  • Top Commenters

  • Popular Threads

  • Recent Comments

    • Small update: the rate that housing in DC is going for Obama's upcoming inauguration, I think we can massively capitalize C&P by renting out the office for the week! I've seen rates...

      7 months ago by Kendall

      in Yes We Can? Yes We Did!

    • I appreciate how difficult that must have been for you, Jim, and I agree that "woohoo" is exactly how I felt too! :>

      7 months ago by Kendall

      in Yes We Can? Yes We Did!

    • Testing Disqus, again... Hopefully it works out this time.

      7 months ago by Kendall

      in Pellet 2.0 RC3

    • As much as I hate to agree with Kendall, I must say WOOOOHOOO!!!

      8 months ago by Jim Hendler

      in Yes We Can? Yes We Did!

    • It's utterly joyous and amazing. The bummer in the joy are the various anti-gay marriage initiatives, including the loathsome Prop 8 in California. I find it hard to believe and sad that people...

      8 months ago by Bijan Parsia

      in Yes We Can? Yes We Did!

Thinking Clearly

Semantics: OWL, RDF, etc.
Jump to original thread »
Author

Billions and billions…

Started by Kendall · 10 months ago

First Franz got the distribution rights to Racer, now they are taking on RDF stores (PDF) with the new version of AllegroCache. Hey, they’ve got a Prolog in there, too.
The “white paper” entitled Processing Billions of RDF Knowledge Triples Made ... Continue reading »

1 comment

  • Arjohn

    3 years ago

    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.
    reply
Please login to comment.
Returning? Login