jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Mueller <muel...@adobe.com>
Subject Re: TreeImpl.isRemove performance problem and possible workaround
Date Wed, 07 Nov 2012 15:53:27 GMT

Yes, I see. My patch is really just a quick hack (my idea was to avoid
creating many HashMaps), but I'm not sure if it will always work correctly.


On 11/7/12 4:02 PM, "Michael Dürig" <mduerig@apache.org> wrote:

>On 7.11.12 14:54, Thomas Mueller wrote:
>> Hi,
>> I think this has been discussed before (but I'm not sure): there is a
>>performance problem in TreeImpl.isRemoved(). I think I found a temporary
>See also the fixme tag in the code: FIXME rely on underlying mechanism
>to determine whether a node has been removed. (OAK-417)
>I'd like to eventually improve this by pushing this functionality down
>to the NodeBuilder. See OAK-417.

View raw message