What kind of information concerning the repository do you need? There are approximately 120K nodes in the repository. The node hierarchy somewhat follows a /a-rootnode/large-subsection/subtypes/year/month/day/content - There are 13 large-subsections - around 5 subtypes per large-subsection - year ranges from 1995-2007 - month (12) - day (depends on the month, and if there is content on that day) - and then there is perhaps up to 10 content items in each day.
I can go deeper into the structure if more information would help. -Dave On 3/13/07, Marcel Reutegger <[EMAIL PROTECTED]> wrote:
David Johnson wrote: > This is related to two ongoing list threads - one on synchronization and > the > other on query performance. > > As I have mentioned in previous posts, I have been running a variety of > query tests. I am using a suite of 100 queries and running them against > Jackrabbit in several different threading scenarios - i.e., I change the # > of threads used to run sub-sets of the 100 queries. To be clear - if I run > a single thread case, it will run all 100 queries, one after the other. If > I run 2 threads - one thread will run 50 queries, while the other thread > will run the other 50 queries. In all cases, the 100 queries are the same, > the only thing that changes is the number of threads used to run them. > Also, in all tests, the repository is read only - nothing is making any > writes to the repository. > > Here are some results: > > 1 thread: 100 queries in 41139 ms > 2 threads: 50 queries in 37828 ms, 50 queries in 38622 ms - total time for > all threads to complete 38960 ms > 4 threads: 25 queries in 25895 ms, 25 queries in 28034 ms, 25 queries in > 32335 ms, 25 queries in 32391 ms - total time 32801 ms > 10 threads: 10 queries in 18733 ms, 10 queries in 19894 ms, ... , 10 > queries > in 33798 ms, 10 queries in 34924 ms - total time 35286 ms > 25 threads: 4 queries in 2413 ms, 4 queries in 11725 ms, 4 queries in 18294 > ms, ... , 4 queries in 36059 ms, 4 queries in 36222 ms > > Some details on the box that I am running these tests on: it is a dual Xeon > running Linux - /proc/cpuinfo shows 4 processors, so I am assuming it is a > dual core. I am running Jackrabbit 1.2.3 with the Bundle Persistence > Manager. > > I am not sure what the numbers above are really saying, although they don't > really look right :-) We have a multi-user use case - large web site with > many ongoing reads, occasional writes. I am using the multiple threads to > "test" multiple users. I am hoping that the developers with more > understanding of the internals can explain what's going on above. > > I am wondering if I am hitting the synchronization issue that is being > discussed in other posts? Thoughts? that's difficult to tell just from the timings and numbers of threads. do you mind sharing your tests classes and post them to the list? we'd also need some information on the content you have in your workspace. regards marcel
