Hi,
On Tue, Sep 24, 2013 at 11:19 PM, Jukka Zitting <jukka.zitt...@gmail.com> wrote:
> On Tue, Sep 24, 2013 at 10:47 PM, Jukka Zitting <jukka.zitt...@gmail.com>
> wrote:
>> The concurrent read and read/write test cases look like more attention
>> is needed on the test code, as it's currently hard to interpret the
>> results. I'll see what I can do there.
>
> It turns out most of the reported time was going to login() calls (see
> OAK-634). I refactored the tests in revision 1526092 so that the login
> calls won't affect the performance measurements.
There were a few other systemic issues with the concurrency benchmarks
(like the background threads running at lower priority and doing less
work). I made some further improvements, and the numbers now look like
this:
# ConcurrentReadTest 90%
Jackrabbit 4132
Oak-Default 2031
Oak-Mongo 2116
Oak-Segment 2258
Oak-Tar 2580
# ConcurrentReadWriteTest 90%
Jackrabbit 3192
Oak-Default 3600
Oak-Mongo 4596
Oak-Segment 2605
Oak-Tar 2876
# ConcurrentWriteReadTest 90%
Jackrabbit 2770
Oak-Default 875
Oak-Mongo 1243
Oak-Segment 565
Oak-Tar 405
# ConcurrentWriteTest 90%
Jackrabbit 597
Oak-Default 2141
Oak-Mongo 1166
Oak-Segment 558
Oak-Tar 348
Full details in https://gist.github.com/jukka/6748243.
BR,
Jukka Zitting
