From: Greg W. <gr...@we...> - 2006-11-30 15:37:24
|
John, a number of responses to this... firstly top is probably not the best measure of java memory usage. You will find that a hello world program is going to eat a fair bit of memory as the JVM is pretty big (although a lot of that is shared libaries). Jetty is small in terms of required code - only 300kB to 700kB depending on what you need to run. This is very good for embedded systems with limited code. Jetty is also small in terms of it's scalable use of memory for buffers. It allocates a pool of big buffers, but then uses them well. So it uses a moderate amount of memory for connection 1, but connections 2 through 10,000 are going to be a lot cheaper. So run up a few thousand clients and compare foot prints. There is also the resource cache that is configured in memory. So just because the demos use memory... does not mean they need memory. cheers johnmc wrote: > Hello, > I’m new using Jetty. I downloaded and ran Jetty 6.x on Linux running Red Hat > with Java 1.5. I was able to connect to the Web Server with no problem and > examples worked. > > I was under the impression that Jetty was designed for small runtime memory > footprint “embedded” and this is the main reason that I decided not to use > Tomcat. > > I’m using the LINUX “top” utility and I find that Jetty uses 36meg RES > memory just running the Jetty examples. I don’t see any improvement over > Tomcat. Am I missing something? Is this memory reported by top correct? > -- Greg Wilkins<gr...@we...> US: +1 3104915462 IT: +39 3349267680 http://www.webtide.com UK: +44(0)2079932589 AU: +61(0)417786631 |