Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of dhrubo.kayal@gmail.com
 designates 209.85.160.170 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=dD7wNbUaVD0khkY8IV8U5LaLSITShlKsqeK1GGWBD9xe+4Ukk37wSlvA757YEJCHdx
         0uCpHNH16edlwbvdUdNMy6KWRFQAgmwrnwTp17av/aPra2DyOj5Pud2bDiZac6qmVzDx
         ykb6DKJJcjS+u3iH46QWBtyZlNuXoJCAHYHJs=
MIME-Version: 1.0
In-Reply-To: 
 <7984D3ED1FAA344FA73D71DC9F54CF2817AB8E11@E03MVX1-UKDY.domain1.systemhost.net>
References: 
 <7984D3ED1FAA344FA73D71DC9F54CF2817AB8E11@E03MVX1-UKDY.domain1.systemhost.net>
Date: Mon, 12 Apr 2010 13:14:36 +0530
Message-ID: <p2xe4b518251004120044n89a77a92u132c7da7832363cb@mail.gmail.com>
Subject: Re: Jackrabbit 1.6.0 Write Performance
From: Dhrubo <dhrubo.kayal@gmail.com>
To: dev@jackrabbit.apache.org
Content-Type: multipart/alternative; boundary=001485f9a5ba0f2e70048405519a

--001485f9a5ba0f2e70048405519a
Content-Type: text/plain; charset=UTF-8

George
If you read the documentation you will see RMI is not the recommended mode
of access. Foo whole EJB saga had so much stories about RMI horrors or
whatever.
Best is to use Jackrabbit in embeded mode and expose Remoting layer like
Rest, etc.

On Mon, Apr 12, 2010 at 1:05 PM, <george.sibley@bt.com> wrote:

>  Hi
>
> We're running a multi-threaded application which creates/updates nodes in
> jackrabbit. Here's an outline of the deployment model:-
>
> - The jackrabbit web app is deployed to the same tomcat instance as our
> main app.
> - The jackrabbit repository is accessed from our app using RMI.
> - We use Threadlocal to confine/isolate the jackrabbit Session.
> - We use jackrabbit node locking to enable concurrency of writes to
> jackrabbit nodes. We have a multiple level node hierarchy where nodes are
> added concurrently.
>
> - We use the embedded Derby database for database persistence.
>
> We're getting a bit of a bottleneck when performing the writes, mainly due
> to the amount of node locking we're having to do. I can't see a way around
> this, so the only measures I can see to improve the performance is speed up
> the writes.
>
> We've tested using postgres for the database persistence, so hopefully we
> should get some performance gains there. Is there anything else that can
> help improve the write performance? E.g. moving back to using the standalone
> server, rather than co-hosting jackrabbit in the same tomcat container as
> the app?
>
> Regards
>
> George Sibley
>
>
>


-- 
Thanks ... Dhrubo
My Book - http://www.apress.com/book/view/1430210095

My Blog -
http://www.jtraining.com/blogs/blogger/dhrubo/

LinkedIn - http://www.linkedin.com/in/dhrubo

--001485f9a5ba0f2e70048405519a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

George<br>If you read the documentation you will see RMI is not the recomme=
nded mode of access. Foo whole EJB saga had so much stories about RMI horro=
rs or whatever.<br>Best is to use Jackrabbit in embeded mode and expose Rem=
oting layer like Rest, etc.<br>
<br><div class=3D"gmail_quote">On Mon, Apr 12, 2010 at 1:05 PM,  <span dir=
=3D"ltr">&lt;<a href=3D"mailto:george.sibley@bt.com">george.sibley@bt.com</=
a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin: =
0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left:=
 1ex;">


<div>


<p><font face=3D"Arial" size=3D"2">Hi</font>
</p>

<p><font face=3D"Arial" size=3D"2">We&#39;re running a multi-threaded appli=
cation which creates/updates nodes in jackrabbit. Here&#39;s an outline of =
the deployment model:-</font></p>

<p><font face=3D"Arial" size=3D"2">- The jackrabbit web app is deployed to =
the same tomcat instance as our main app.</font>

<br><font face=3D"Arial" size=3D"2">- The jackrabbit repository is accessed=
 from our app using RMI.</font>

<br><font face=3D"Arial" size=3D"2">- We use Threadlocal to confine/isolate=
 the jackrabbit Session.</font>

<br><font face=3D"Arial" size=3D"2">- We use jackrabbit node locking to ena=
ble concurrency of writes to jackrabbit nodes. We have a multiple level nod=
e hierarchy where nodes are added concurrently.</font></p>

<p><font face=3D"Arial" size=3D"2">- We use the embedded Derby database for=
 database persistence.</font>
</p>

<p><font face=3D"Arial" size=3D"2">We&#39;re getting a bit of a bottleneck =
when performing the writes, mainly due to the amount of node locking we&#39=
;re having to do. I can&#39;t see a way around this, so the only measures I=
 can see to improve the performance is speed up the writes. </font></p>


<p><font face=3D"Arial" size=3D"2">We&#39;ve tested using postgres for the =
database persistence, so hopefully we should get some performance gains the=
re. Is there anything else that can help improve the write performance? E.g=
. moving back to using the standalone server, rather than co-hosting jackra=
bbit in the same tomcat container as the app?</font></p>


<p><font face=3D"Arial" size=3D"2">Regards</font>
</p>
<br>

<p><font face=3D"Arial" size=3D"2">George Sibley</font>
</p>

<p><font face=3D"Arial" size=3D"2">=C2=A0 </font>
</p>

</div>
</blockquote></div><br><br clear=3D"all"><br>-- <br>Thanks ... Dhrubo<br>My=
 Book - <a href=3D"http://www.apress.com/book/view/1430210095">http://www.a=
press.com/book/view/1430210095</a><br><br>My Blog - <br><a href=3D"http://w=
ww.jtraining.com/blogs/blogger/dhrubo/">http://www.jtraining.com/blogs/blog=
ger/dhrubo/</a><br>
<br>LinkedIn - <a href=3D"http://www.linkedin.com/in/dhrubo">http://www.lin=
kedin.com/in/dhrubo</a><br>

--001485f9a5ba0f2e70048405519a--