![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgnZ7Vuh3xHfWiN2GHRpZ2oJnZlnb_yMgYI_mg7dLRKumFdSxgAkBXHRm_Nw2r-IkNbdBvV0l_XQS3WjyqRXRbtG5bMtyezd8Bg_21lIV73nAxZFqqzdgzDCy1YlWN8f-ZLsxvKeoRrLEUc/s320/growthchartuse.gif)
Tue, 11 Sep 2007 06:40:50 -0700
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/libs2. 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
No comments:
Post a Comment