Hi Giancarlo, First of all thank you very much for such a detailed response, I really appreciate that and sorry to get back to you late.... actually I was away for few days.
However, I got things working by putting them in their own JVMs using Catalina_Base. Also I found some weired behaviors by using different jdks.. like with jdk 1.6 i was able to run three magnolia apps in one tomcat instance with jdk 15.7 four and with jdk 1.4.2 i was able to run 6 apps.... but i really didnt want to go this stupid way.... so i put each magnolia app in its own jvm using Catalina_Base. Also putting things in own JVMs has significantly enhanced the response time. Yes we have different DNS for all the sites as they are independent of each other but most of them are resolving to same IP (they are sitting on the same server).... what we really wanted is to have one author instance having multiple sites in it. But i couldn't get my head round it... there is some info on wikki pages but not enough and also i was also tight on schedules so i thought to go this way. But i am still interested in having one author instance for multiple websites... So how this would work actually would every website be having its own users, roles, config...... can you please guide me....??? Best regards, Salman Magnolia - User mailing list wrote: > > Hi Salman > > Just my 2cts. > > 1) Why are you creating an Author and a Publish instance for each > site? Does each of the mini sites have a different DNS or IP address? > If not, you can add a new website easily by just starting again from > Website's /. You then can create Groups and Roles for each of these > sites and protect them against other authors. Typically, you have > just one Author instance for all sites. Multiple instances are > usually redundant and managed by a load balancer to create a "fail- > safe" system and tune performance. > > 2) Perm Size is similar to the famous Heap Size. The Perm space is > used by the JVM to manage the thread and method-call stack. So the > more threads and methods are running, the more stack space you will > need. Usually, 64MB is sufficient, but to be on the sure size you can > set it to 128MB. However, the more perm size you have, the slower it > gets! > To set the Perm Size you have to use TWO settings: -XX:PermSize=128m - > XX:MaxPermSize=128M. Only with these two settings you will get the > higher PermSize. > > 3) The min and max Heap size can be set equally. The min heap size is > what the JVM will start with. If required, the JVM will allocate more > memory in slices until it reaches the max heap size. So if you want > to tweak a little on the performance, you might want to set both, min > and max to the same value. > > 4) It's actually not Magnolia which is the memory pig! The > persistence managers used by Jackrabbit are the big memory eaters, > especially the default db PM. So if you can not set the heap to 768MB > or 1024MB, you may want to replace the PM with the FileSystem PM, > which utilizes the least heap memory. The reason why Magnolia ships > by default with the DB persistence managers is for licensing reasons. > > Salman, I don't know if this solves any problems, but I hope it helps > a little. > > Cheers > > Giancarlo > www.xumak.com > ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/developer.html ----------------------------------------------------------------
