Hi Jukka, First, thanks for the information. I think you explained what the numbers mean (seconds, milliseconds, etc.) in a previous email, but I can't locate it.
Can you briefly explain the test results or point me to a wiki or link that has the explanation? Thanks, Michael -----Original Message----- From: Jukka Zitting [mailto:[email protected]] Sent: Friday, May 31, 2013 8:14 AM To: Oak devs Subject: Re: Some more benchmarks Hi, On Fri, Apr 26, 2013 at 2:12 PM, Jukka Zitting <[email protected]> wrote: > On Wed, Mar 27, 2013 at 11:41 AM, Jukka Zitting <[email protected]> > wrote: >> Here's a few more simple benchmark results to show where we are: > > Updated numbers with latest Oak: And another one: Apache Jackrabbit Oak 0.9-SNAPSHOT # ReadPropertyTest min 10% 50% 90% max N Jackrabbit 41 41 42 43 90 1428 Oak-Default 58 58 59 60 69 1018 Oak-Mongo 66 67 67 68 74 889 Oak-Segment 278 279 281 285 321 213 Oak-Tar 114 114 115 117 136 520 # SmallFileReadTest min 10% 50% 90% max N Jackrabbit 56 57 61 84 194 895 Oak-Default 57 57 59 304 353 594 Oak-Mongo 148 148 158 406 479 304 Oak-Segment 33 33 36 37 73 1701 Oak-Tar 15 15 16 18 31 3574 # SmallFileWriteTest min 10% 50% 90% max N Jackrabbit 184 196 248 444 2084 115 Oak-Default 136 138 181 433 1789 162 Oak-Mongo 595 617 795 1020 1075 31 Oak-Segment 156 161 172 225 660 100 Oak-Tar 101 102 108 116 270 167 (also available at https://gist.github.com/jukka/5684506 if the above gets mangled with a variable-width font) It looks like we have a performance regression in ReadPropertyTest. Quick profiling shows a lot of the time seems to be going to MemoryNodeBuilder$ConnectedHead.update(), which is weird since we're only reading and thus the related MNB head should be unconnected. I'll investigate. BR, Jukka Zitting
