Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <1437637391.1250004855041.JavaMail.jira@brutus>
Date: Tue, 11 Aug 2009 08:34:15 -0700 (PDT)
From: =?utf-8?Q?Michael_D=C3=BCrig_=28JIRA=29?= <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Resolved: (JCR-2218) NodeEntryImpl.getWorkspaceId() very
 inefficient
In-Reply-To: <1713789777.1247752934828.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/JCR-2218?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael D=C3=BCrig resolved JCR-2218.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0

Applied path in revision 803164

> NodeEntryImpl.getWorkspaceId() very inefficient=20
> ------------------------------------------------
>
>                 Key: JCR-2218
>                 URL: https://issues.apache.org/jira/browse/JCR-2218
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-jcr2spi
>            Reporter: Michael D=C3=BCrig
>            Assignee: Michael D=C3=BCrig
>             Fix For: 2.0.0
>
>         Attachments: JCR-2218.patch
>
>
> NodeEntryImpl.getWorkspaceId() calculates its path on each call by callin=
g itself recursively. Further each call to getWorkspaceId() results in vari=
ous calls to the path and item factories which might be somewhat expensive =
by themselves.=20
> In my test scenario I have a RepositoryService.getItemInfos() call return=
ing ~1000 items. Processing these items results in about 2700000 (!) calls =
to getWorkspaceId(). Profiler data shows, that 98% of the time to process t=
he 1000 items is spent in getWorkspaceId()  and related calls.=20

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.