On 2010-02-18 11.02, Stanislav Muhametsin wrote:
I was creating I'd say around thousand entities in one uow, before I
divided it to do same work in many smaller uow's.
I managed to make the profiler work again (somewhat), it's still
unstable as hell. So far it seems that even when doing 200 entities test
(new uow, creating 200 entities, completing uow, new uow, deleting 200
entities, completing uow), the execution time for test is around 7sec or
so. And around 40sec when profiling. That's terribly slow (IMO), and I'm
no longer sure why - 50% of execution time are lost "somewhere", and
profiler doesn't know where. And I'm unable to make that
getExclusiveLock() to show up in results anymore (with 200 entities).
Maybe it is confused because of Qi4j's class generation. This needs
further research...
Can you make a simple test: remove the RDF indexing from your app, so
that only your UoW code and the EntityStore is running. Are you then
seeing the same performance? Is the problem in Qi4j or are we looking at
Sesame being the culprit is what I'm wondering?
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
