-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Manfred Tremmel wrote:
Am Donnerstag, 14. September 2006 21:34 schrieb Pascal Bleser:
Andreas Jaeger wrote:
to 1.5.0 on my knightsoft-net Webserver, it needs to much memory for the small vserver. The same bytecode uses more RAM when running with 1.5 than with 1.4 ?
The virtual machine needs more RAM to start, so I don't have enough space left for my own servlets. I've rent the smalest version of the VServer which is very limited in ram (in the FAQ the provider says it's to small for tomcat, I never could belive it ;-) ). Using java 1.5 I can watch two generated pages, the third one ends with a out of memory entry in the logfils. Using java 1.4.2 it works stable without a problem, even with high loads.
http://java.sun.com/j2se/1.5.0/docs/guide/vm/gc-ergonomics.html
Just start the 1.5 JVM with
- -Xmx64m
and you will have the same heap size as the default heap size on 1.4
Tiger (1.5) is definitely faster than 1.4 (even with 1.4 bytecode, it's
really the JVM that's faster), it should just be a matter of configuring
the maximum heap size (and possibly the thread stack size (-Xss)), as
the defaults have changed (see URL above).
If you use the 1.5 JVM, you should really try out Tomcat 5.5, it has
vast improvements, if you don't already use that version now.
As a replacement for Tomcat, Winstone should have lower demands in terms
of resources: http://winstone.sourceforge.net/
(dual-license LGPL/CDDL; it supports servlet 2.5, AJP, vhosting, SSL,
JNDI, clustering, etc... - for JSP support, you must add Tomcat's
Jasper, but that's documented)
Jetty should be memory-friendlier than Tomcat as well:
http://jetty.mortbay.org/
Though it's perfectly fine to run Tomcat with just 64MB. We've got JIRA
running in production (around 80 users, overall) with Tomcat and 64MB.
(but I'm afraid we're drifting into off-topicness, sorry for the noise,
but could be helpful information to others)
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\