On 2/13/07, Justin Pizzala <[email protected]> wrote:
Tom,
We are just using the default persistence mechanism for Magnolia 3
(jackrabbit).
I think the question was more about: what underlying persistence
mechanism are you using (BerkleyDB, Apache Derby, XML, etc.).
./alex
--
.w( the_mindstorm )p.
Justin Pizzala
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
Sent: Friday, February 09, 2007 2:56 PM
To: [email protected]
Subject: Re: [magnolia-user] Magnolia 3 Excessive Export Times
CRM:00050069
Hi,
On Feb 9, 2007, at 12:19 PM, Justin Pizzala wrote:
> There are only about 15 pages being exported for the website
> repository.
> We are also exporting config, dms, users, usergroups, and userroles.
> None of which have an exceptional number of nodes, but each of which
> take over five minutes to compile and export.
I am also seeing significantly increased export times even on very
small sites. A tiny 4 page site with hardly any content takes
several minutes to export. I'm using Magnolia 3.0.1 w/bdb
persistence mechanism.
Unfortunately, I do not have an answer, but it seems important that
we get to the bottom of this to make sure we can reliably backup and
restore our sites. Which persistence mechanism are you using?
Tom
> -----Original Message-----
> From: [email protected] [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 09, 2007 10:06 AM
> To: [email protected]
> Subject: Re: [magnolia-user] Magnolia 3 Excessive Export Times
> CRM:00050069
>
> Hi Justin,
>
> roughly how many pages are you talking about, just out of interest? If
> that's the case I'd rather shut dsown the server for five minutes and
> copy the whole kit and kaboodle into a backup directory. Sounds
> safer to
> me than having a live repository bombing on me and getting
> corrupted in
> the process...
>
> Or am I overreacting?
>
> Frank Sattler.
>
> -----Original Message-----
> From: [email protected] [mailto:[EMAIL PROTECTED]
> Sent: 09 February 2007 17:47
> To: [email protected]
> Subject: [magnolia-user] Magnolia 3 Excessive Export Times CRM:
> 00050069
>
> Hello,
>
> We are having an issue with the repository export process in
> Magnolia 3
> using both the adminCentral export tool and the wget console command
> found in the wiki. The process operates similarly on both Windows and
> Linux platforms. The repositories are generated just fine, but they
> take
> over five minutes each to export. In Magnolia 2.1.x, the export
> time was
> minimal. We monitored the system resources during one of these export
> activities and found that the server was using ~1Gb memory (with
> ~500Mb
> swap on top of this). Is this a normal occurrence for 3.0? Has any one
> else had this problem or could it be a setting that we overlooked? Any
> suggestions as to how to make this process more efficient or will we
> have to wait for a future release?
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
