Java web apps have always been memory hungry, but that's the price you have to pay to gain performance or anyone reasons you have to use java/grails... And tuning JVM usually requires some skills, but there are some basic steps that should help for a while at least. But I would not worry about that until you have an actually problem.
Hosting multiple web apps under one container instance is pretty common I'd say, you just have to make sure all your java web apps have enough memory, thus test/profile your apps... The WAR's size may not mean high memory usage, it's the contents that matter...
You don't have to restart your tomcat instance to re-deploy your app. All you have to do is to replace deployed war with your new build and it will auto-deploy for you... It also has some basic web interface to do that... from where you can stop/start/restart your apps... and so on.
On Sun, Aug 12, 2012 at 8:57 AM, marc.esher
<[hidden email]> wrote:
Greetings all,
Coming from a dynamic / interpreted language background (ColdFusion, PHP,
etc), it's common to write multiple applications and host them within the
same container without much trouble.
I'm writing to learn what performance implications I need to consider, best
practices, and other advice for running multiple Grails applications within
a single tomcat. Considering that even a simple .war is 30 MB, I'm concerned
about heap, permgen, etc. I'm also concerned about reload implications: I
don't want to restart tomcat -- and thus bring down all apps -- if I'm
deploying a new version of Application A.
Advice / guidance appreciated.
Marc
--
View this message in context: http://grails.1312388.n4.nabble.com/Performance-implications-and-advice-for-running-multiple-Grails-applications-in-a-single-Tomcat-tp4633073.html
Sent from the Grails - user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Locked
