Hi,
On Tue, Sep 24, 2013 at 10:47 PM, Jukka Zitting <[email protected]> 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. As a result the
numbers look much better:
# ConcurrentReadTest 90%
Jackrabbit 447
Oak-Default 286
Oak-Mongo 240
Oak-Segment 245
Oak-Tar 252
# ConcurrentReadWriteTest 90%
Jackrabbit 383
Oak-Default 263
Oak-Mongo 270
Oak-Segment 280
Oak-Tar 268
BR,
Jukka Zitting
