On 9/20/06, Jukka Zitting <[EMAIL PROTECTED]> wrote:
Hi,
On 9/20/06, Alexandru Popescu <[EMAIL PROTECTED]> wrote:
> The second approach was to manually navigate the parent child nodes,
> read just a couple of properties in the first place so that I do
> manually the filtering, and only afterwards fetch the entire node
> properties.
>
> Once again, the performance is going down 2-3 order of magnitude (from
> hundreds of ms down to ten thousands (even hundred thousand) ms).
Hmm, could you send the test case you are running? I just did a
concurrency test that reads a property from random locations within a
content tree of 10k nodes. The property access time is nicely linear
with concurrent threads, each thread taking about 18s of wall clock
time to read 1000 properties with 100 concurrent threads running on my
laptop.
I will try to trim down my functional test. Still, I am missing the
repository creation/load fixture, so I will highly appreciate if you
can share this one (and I don't have to write it my own :-( ).
thanks in advance,
./alex
--
.w( the_mindstorm )p.
BR,
Jukka Zitting
--
Yukatan - http://yukatan.fi/ - [EMAIL PROTECTED]
Software craftsmanship, JCR consulting, and Java development
