jackrabbit-oak build #1703: Fixed

2013-06-06 Thread Travis CI
Build Update for apache/jackrabbit-oak - Build: #1703 Status: Fixed Duration: 1602 seconds Commit: 924baad7277f7fc75c699d98f4d17f0586655cfc (trunk) Author: Jukka Zitting Message: OAK-799: Fail-fast for content diffs Streamline EditorDiff to reduce the number o

jackrabbit-oak build #1702: Broken

2013-06-06 Thread Travis CI
Build Update for apache/jackrabbit-oak - Build: #1702 Status: Broken Duration: 669 seconds Commit: fb96bd6b92e3f3fff91bc9fb92cc5987d2715e96 (trunk) Author: Jukka Zitting Message: OAK-641: Improved benchmark tooling Better formatting of hprof analysis reports

jackrabbit-oak build #1700: Broken

2013-06-06 Thread Travis CI
Build Update for apache/jackrabbit-oak - Build: #1700 Status: Broken Duration: 1150 seconds Commit: fa27d3c33ea57a8f3b34bceb12937b8b6a28ce3b (trunk) Author: Thomas Mueller Message: OAK-13 Use a daemon thread to avoid blocking the build. git-svn-id: https://svn

Re: svn commit: r1490258 - /jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/memory/MemoryNodeBuilder.java

2013-06-06 Thread Jukka Zitting
Hi, On Thu, Jun 6, 2013 at 4:01 PM, Michael Dürig wrote: > On 6.6.13 13:41, ju...@apache.org wrote: >> private Head head() { >> -return head.update(); >> +Head newHead = head.update(); >> +if (newHead != head) { >> +head = newHead; >> +} >> +

Re: svn commit: r1490258 - /jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/memory/MemoryNodeBuilder.java

2013-06-06 Thread Michael Dürig
On 6.6.13 13:41, ju...@apache.org wrote: Author: jukka Date: Thu Jun 6 12:41:28 2013 New Revision: 1490258 URL: http://svn.apache.org/r1490258 Log: OAK-781: Clarify / fix effects of MISSING_NODE as base state of NodeBuilder Fix the performance issue of a ConnectedHead never actually updating

Re: Some more benchmarks

2013-06-06 Thread Jukka Zitting
Hi, On Fri, May 31, 2013 at 3:14 PM, Jukka Zitting wrote: > 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

Re: NodeBuilder#setProperty using the same value

2013-06-06 Thread Michael Dürig
On 5.6.13 13:43, Jukka Zitting wrote: Hi, On Wed, Jun 5, 2013 at 3:32 PM, Alex Parvulescu wrote: I'm wondering if we could turn the NodeBuilder#setProperty into a noop when setting the same value on a property. I don't see any bigger issues with this, though it would be nice to have a benc