Frank, 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.
We are unable to shutdown the server to copy the contents to a backup machine. Primarily, because this site is in production and up time is crucial. Secondarily, because we need this process to be automated and sent to the backup server as a single, compact zip file (which is currently initiated with a shell script). Also, (and this is something I foolishly forgot to include in my first post) the CPU usage is peaking near 98% during this export process as well. Hopefully this sheds new light to the situation? Thanks for your reply. Justin Pizzala tel | fax 888 - 259 - 7345 x84 -----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? Thanks in advance. Justin Pizzala ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ---------------------------------------------------------------- ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
