Gang, I have just noticed that Sesame/OpenRDF has a general performance problem when it comes to removing so called "connections", i.e. when we Remove an Entity from the entity store, the index needs to be updated. This takes on my machine 360ms per entity if I do a batch of 1000 removals per connection.commit() (~6 minutes). The total graph consist of ~20,000 entities.
Interestingly enough, the call to connection.clear() is slow, but the commit() is relatively fast (5 sec of the total). I am getting more and more annoyed by OpenRDF/Sesame, and seriously considering implementing and alternate Indexing engine. Problem is; It will take more time than I have for the 1.0 release. Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
