Tarek,
On 10/29/2018 2:04 AM, Leon Rosenberg wrote:
Clearly one webapp per tomcat. Makes everything easier. Also, if your
apps aren't really tiny, the memory overhead of tomcat is minimal
compared to the advantages.
+1
On 10/29/2018 6:39 AM, Christopher Schultz wrote:
I usually deploy one webapp per JVM/tomcat instance. I do this so that
a problem in one webapp doesn't take-down the others. It's as simple
as that. The other benefits are being able to service that one JVM
without taking down N webapps -- just one, and also being able to run
under different JVMs, system libraries, etc. without having to test
each application for compatibility.
+1
Also, if you end up with a much larger heap because you put a bunch of
applications together, then you can run into longer GC cycles (can
happen even with concurrent garbage collectors). When you have a Full
GC, all of your applications' threads stop, and if it takes long enough,
i.e. more than a fraction of a second, the lack of responsiveness of the
applications will become noticeable.
The whole is greater than the sum of its parts, just that in this case
"greater" is a bad thing.
Igal
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
