jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandru Popescu" <the.mindstorm.mailingl...@gmail.com>
Subject possible performance problem (need a way to test it)
Date Mon, 18 Sep 2006 15:17:53 GMT

I have identified a possible performance problem with high concurrency
querying against JCR. Still, I would like to have an easy way to
reproduce it, so that I can profile it. I am wondering if there are in
the Jackrabbit source base good samples on how to set up a quick
testing repository.

This was the first part. Now about the real problem I am seeing: when
accessing the JCR repo from multiple concurrent threads (each using
its own Session) and we perform querying we see a huge CPU load and
the response times are growing very fast:
- for 5 concurrent threads the query reponse times are around 200-500
ms; server load about 0.65-0.7
- for 100 concurrent threads the query response times are around
150000-200000 ms; server load about 7-7.5

As you can see these are very dangerous numbers, and I would
definitely like to figure out what is the problem behind them, because
in my application I can expect something around 300 concurrent threads

I know I can start looking at different options like caching and
similar ideas, but firstly understanding the real problem will help me
a lot.

Many thanks for any helping ideas and comments,

:Architect of InfoQ.com:
 .w( the_mindstorm )p.
Co-founder of InfoQ.com

View raw message