Is there a serious, complete i. Quick rundown of some information out there comparing the native triple store solutions of Jena and Sesame.
Summarising numbers crunched by Bizer et al. Chris Bizer, Andreas Schultz. Semantic Web Inf. Can only find references to unverified claims on the ESW wiki :. Note that Sesame is demonstrated to load M in the previous evaluation, and the older claim of 70M is based on pretty underpowered hardware.
First of all, both Sesame and Jena support multiple storage backends with highly different performance characteristics. Second, part of the strength of Sesame and I expect Jena as well is its ability to provide a storage-independent API, that allows you to easily switch backend without having to change your client code.
So, in my opinion, a useful part of a comparison would be to show how the two frameworks solve certain common tasks: e. Having code examples for such simple tasks side-by-side seems useful to me. If someone were to set up something like this, I'd be happy to try and contribute some code examples. Here's my take. I don't use either Jena or Sesame as a persistent triple store and don't expect to ever do so.
On the other hand, I do have a need for something that handles a small number of triples say typically and 1M in an extreme case in RAM. I don't want to deal with setup and teardown time for a "big" triple store. I do care about feature support, and I think Jena wins that hands down.
