jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg" <stefan.guggisb...@day.com>
Subject Re: InMemPersistenceManager hogging resources
Date Wed, 06 Aug 2008 09:56:08 GMT
On Mon, Aug 4, 2008 at 9:18 PM, Jared Graber <jared.graber@iaccap.com> wrote:
> It seems to me that this renders the InMemPersistenceManager unusable except for unit
testing (which is works really well for).


please note the last sentence (bold) of the class description ;)


> None of the properties contain a lot of data - mostly 10 chars or less, in rare cases
(less than 100 nodes) they would break the 50 character mark and even then it's probably maxing
out at around 500 characters.  I'm not sure data compression would really help.
> It looks like there is a great deal of memory overhead with the jackrabbit objects because
there isn't that much actual data.
> -Jared
> -----Original Message-----
> From: tmueller@day.com [mailto:tmueller@day.com] On Behalf Of Thomas Müller
> Sent: Monday, August 04, 2008 2:50 PM
> To: users@jackrabbit.apache.org
> Subject: Re: InMemPersistenceManager hogging resources
> Hi,
>> When I exported the content to an XML file, it was about 15MB.
>> When I imported the data into the repository my webapp climbs to 800MB
>> Is this normal?
> I think yes, unfortunately. One idea to solve is to add data
> compression to the InMemPersistenceManager. I'm not sure how much that
> would save however.
> Regards,
> Thomas

View raw message