On 2010-02-18 11.50, Niclas Hedhman wrote:
On Thu, Feb 18, 2010 at 11:47 AM, Stanislav Muhametsin
<[email protected]> wrote:
It's 05:40 AM and I think it's time to sleep. ;) One thing the profiler
could tell me certainly: the notifyChanges() method in
RdfIndexingService.RdfEntityIndexerMixin is taking most time (around 60-80%)
when performing this test. So, it's somewhere in OpenRDF... the question
lies, where. :) I poked around some code but didn't find anything specific.
Althought the removing seems pretty heavy operation - it starts
transactions, iterates over a lot of stuff, etc... Dunno, maybe it is
supposed to be like that, but currently it is slow as hell. And I even have
a what is considered a proper computer, with SSD drive (proper, Intel one).
So I don't think it should be HW-related either.
I agree. I have also noticed huge performance problems in general, and
GutFeeling says it is not short-term solvable by keeping Sesame as a
strategic component.
I'd like to send this observation to the sesame-dev mailing list, and
ask if they have any suggestions.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
