Hello Baber,
there are several options to improve performance issues (which by the
way do not depend on Magnolia itself but on the underlying
infrastructure of your setup):
We recommend the following:
First, switch the underlying persistence provider to something other
than Derby, e.g. use BerkeleyDB or MySQL. To do so perform the
following steps:
1. Copy magnolia-berkeley-1.0.jar* (see below) to WEB-INF/libs
2. Place java implementation of berkeley db under WEB-INF/lib, you
can download this from
http://www.oracle.com/database/berkeley-db/je/index.html
3. Modify WEB-INF/config/default/magnolia.properties to use magnolia-
berkeley persistence.
change --> magnolia.repositories.jackrabbit.config=WEB-INF/
config/repo-conf/jackrabbit-derby-search.xml
to --> magnolia.repositories.jackrabbit.config=WEB-INF/
config/repo-conf/jackrabbit-bdb-search.xml
NOTE :
(a) You cannot change the persistence manager of the already
initlized jackrabbit repository, you must
configure this before the bootstrap process.
(b) To configure this in already initialized repository:
- export all data to xml
- configure (step 1,2,3)
- remove existing repository physically from the file
system
- bootstrap using previously exported files.
*using the Enterprise Edition, you can find the .jar file in
MAGNOLIA_EE_HOME/add-ons/magnolia-bdb-1.0/
Second, we recommend you to upgrade to the latest version of the
Magnolia, currently Magnolia 3.0.3. With Magnolia 3.0.3 you can
safely change the underlying Jackrabbit (JCR) implementation to
version 1.3.1 (which is 1.0.1 by default). To do so refer to the
instructions given in TOMCAT_HOME/webapps/magnoliaAuthor/WEB-INF/
config/repo-conf-jackrabbit-1.3/readme.txt. Note that there are
already properly configured files in that directory, which should
make the transition to the new version of Jackrabbit very easy.
Finally, something that you should take note about as well: in
general, using Tomcat, you should not reload your web applications
with Tomcat's admin console web application. When restarting the
Magnolia instance with that tool the memory used before is not
released properly, which can lead to very bad performance as well.
Instead do a full restart of Tomcat to avoid those issues.
Regards,
Vivian Steller
Magnolia International Ltd.
------------------------------------------------------------------------
---------
[EMAIL PROTECTED] http://www.magnolia.info
Magnolia® - Simple Enterprise Content Management
------------------------------------------------------------------------
---------
Am 10.09.2007 um 19:15 schrieb Baber Shah:
Hi,
I would like some advice regarding performance issues.
A brief description of our environment follows:
We have an environment that is load balanced between two servers -
Dual
Processoor Xeons running at 3.4 GHz and with 8 GB RAM
Each server hosts a pair of Magnolia instances (one Author and one
Public) and each instance of Magnolia is configured with 3 subscribers
(it's parnet instance and the pair of Magnolias on the other server)
We are running Magnolia 3.0 EE with the standard Derby database and
running on Tomcat 5.0.28. The Tomcats are also used for our website
however server response time is not an issue.
What we are finding is that Magnolia performance is good under very
little load (ie. a single user making changs and activating the
workflow) However when we have multiple users making updates then the
performance falls off dramatically (perhaps linearly).
What I want to know is if there are any tweaks we can make to our
setup
or components we can upgrade (the backend) which will improve
performance ?
It would be very helpful if someone could descibe what potential
bottlenecks there are in a Magnolia environment and how they can be
circumvented ?
Baber Shah
Associate
Core Data
Markit
Level 5
2 More London Riverside
London SE1 2AP
+ 44 20 7260 2139 Office
+ 44 20 7260 2001 Fax
[EMAIL PROTECTED]
www.markit.com <http://www.markit.com/>
The content of this e-mail is confidential and may be privileged.
It may be read, copied and used only by the intended recipient and
may not be disclosed, copied or distributed. If you received this
email in error, please contact the sender immediately by return e-
mail or by telephoning +44 20 7260 2000, delete it and do not
disclose its contents to any person. You should take full
responsibility for checking this email for viruses. Markit reserves
the right to monitor all e-mail communications through its network.
Markit and its affiliated companies make no warranty as to the
accuracy or completeness of any information contained in this
message and hereby exclude any liability of any kind for the
information contained herein. Any opinions expressed in this
message are those of the author and do not necessarily reflect the
opinions of Markit.
For full details about Markit, its offerings and legal terms and
conditions, please see Markit's website at http://www.markit.com
<http://www.markit.com/> .
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
