Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 24503 invoked from network); 6 Aug 2008 14:15:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Aug 2008 14:15:54 -0000 Received: (qmail 10611 invoked by uid 500); 6 Aug 2008 14:15:51 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 10598 invoked by uid 500); 6 Aug 2008 14:15:51 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 10585 invoked by uid 99); 6 Aug 2008 14:15:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Aug 2008 07:15:51 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [12.193.211.24] (HELO SITE3MAIL05.jeeves.ask.info) (12.193.211.24) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Aug 2008 14:14:56 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: InMemPersistenceManager hogging resources Date: Wed, 6 Aug 2008 10:15:18 -0400 Message-ID: In-Reply-To: <90a8d1c00808060256h56b512bva4a42a32a70b95ad@mail.gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: InMemPersistenceManager hogging resources Thread-Index: Acj3qrn/N/nIWhsNQt+4pRWDEJ9cHwAI6xpA References: <91f3b2650808041149s3440dcaal674203a486a3c5c3@mail.gmail.com> <90a8d1c00808060256h56b512bva4a42a32a70b95ad@mail.gmail.com> From: "Jared Graber" To: X-Virus-Checked: Checked by ClamAV on apache.org As it turns out, a bunch of the persistent managers use a boatload of = memory during an import. The InMemPersistenceManager is probably the worst (as expected), but = even the Oracle9PersistenceManager (a bundle persistence manager) uses a = few hundred MB. -Jared -----Original Message----- From: stefan.guggisberg@gmail.com [mailto:stefan.guggisberg@gmail.com] = On Behalf Of Stefan Guggisberg Sent: Wednesday, August 06, 2008 5:56 AM To: users@jackrabbit.apache.org Subject: Re: InMemPersistenceManager hogging resources On Mon, Aug 4, 2008 at 9:18 PM, Jared Graber = wrote: > It seems to me that this renders the InMemPersistenceManager unusable = except for unit testing (which is works really well for). http://jackrabbit.apache.org/api/1.3/org/apache/jackrabbit/core/persisten= ce/mem/InMemPersistenceManager.html please note the last sentence (bold) of the class description ;) cheers stefan > 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=FCller > 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 >