Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of 1111software@gmail.com
 designates 209.85.198.238 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:references;
        b=gEoY+mwZeap+1wgMoXz4XFTvg9nMR8gw6LjHYdk/DnGDnxjVutAbOAM0A7eU0vbX+C
         zmOe2eyXc0z7teZPsT9C8f+QD2tC6U81wOgxHCArKfwe7adbZHGBmDiy7c7UqoEBxiEP
         YBSScsoDoMuCqFvzgIf0y8AYS3ndYbDgWbeS8=
Message-ID: <fd7bdf180810070546y500f3bdcp3f6a3a926c2ef1f1@mail.gmail.com>
Date: Tue, 7 Oct 2008 14:46:59 +0200
From: "Jacco van Weert" <1111software@gmail.com>
To: users@jackrabbit.apache.org
Subject: Re: Jackrabbit's memory use
In-Reply-To: <91f3b2650810070244w7e6dc81ah4bfb059610d33bf0@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_73840_5687990.1223383619162"
References: <fd7bdf180810070221i397f42car37a9d5737bd4525a@mail.gmail.com>
	 <91f3b2650810070244w7e6dc81ah4bfb059610d33bf0@mail.gmail.com>

------=_Part_73840_5687990.1223383619162
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hello,

 setMaxMemory(1) helped "a bit".... by the way without the cache the
repository isn't that slow.
In my example 21 seconds with the cache against 26 seconds without it.

But the memory usage stays the same. Looking at the profiling information I
think it is ItemStateCache which caches a lot of data, I don't see an publi=
c
reachable method to purge the cache?
Are more caches?

Gr.

   Jacco


On Tue, Oct 7, 2008 at 11:44 AM, Thomas M=FCller <thomas.mueller@day.com>wr=
ote:

> Hi,
>
> I don't know of a way to completely clear the cache, except the
> obvious 'close the repository'.
>
> There is a way to reduce the cache size however:
>
> ((org.apache.jackrabbit.core.RepositoryImpl)rep).
>  getCacheManager().
>  setMaxMemory(1);
>
> This will however be applied immediately. The cache size is applied
> once a second at most, and is triggered by
> CacheManager.cacheAccessed(). Don't forget to change the size back to
> the old value afterwards, otherwise the repository will be very slow.
>
> Regards,
> Thomas
>
>
> On Tue, Oct 7, 2008 at 11:21 AM, Jacco van Weert <1111software@gmail.com>
> wrote:
> > Hello,
> >
> > For some time I am trying to master to memory use of Jackrabbit.
> >
> > I am using Jackrabbit in a webserver application (JeCARS).
> >
> > When started and accessing nodes there are a couple of megabytes in use=
,
> > regardless of the size of the repository itself.
> > At a certain time I run the "JeCARS internal" garbage collector to remo=
ve
> > expired JCR nodes and also run the Datastore GC.
> > After it is finished, the memory in use is dramatically higher.... this
> > because the Datastore checks every node in the repository, but it doesn=
't
> > falls back (cache?)
> >
> > My question, is there a way to "clear the cache" to reclaim the memory?
> > Were is memory cached?.... session logout doesn't seem to help.
> >
> >
> > Greetings,
> >
> >   Jacco
> >
> >
> >
> > --
> > -------------------------------------
> > Jacco van Weert -- 1111software@gmail.com
> > JCR Controller -- http://www.xs4all.nl/~weertj/jcr
> > JeCARS -- http://jecars.sourceforge.net
> >
>


--=20
-------------------------------------
Jacco van Weert -- 1111software@gmail.com
JCR Controller -- http://www.xs4all.nl/~weertj/jcr
JeCARS -- http://jecars.sourceforge.net

------=_Part_73840_5687990.1223383619162--