Pier Fumagalli wrote:
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:So, My first question is : why tomcat use all the memory while there is no users connected (or just one) ?
You should first see if your application is not eating memory.
My second question is : how much memory is needed if I want to use tomcat with many users (500, 1000,...) ?
The question should be 'how many concurrents users' ?
On a 5 millions hits/day server (not running Tomcat, another servlet container since Tomcat doesn't work for us), we have the VM starting with 1 Gigs of RAM ("java -server -Xmx 1024m -Xms 1024m ...") but we use half of it (roughly) to cache data from the DB...I already read in the forum Tomcat don't manage the memory, it is the JVM... so why the jvm use so many processes ?
Also you could have many threads if you're using ajp13 connectivity since there is one thread by connection with server.
On Linux threads are +/- process and are really cheap to create, so it'sThose are _not_ processes, they are threads... Use a decent operating system that supports them nicely (not Linux) and you'll see the difference (how many times do I have to repeat this?)... Linux sucks :-(
should be a problem.
And if you have problem handling load with one Linux boxes, just use more Linux boxes and use jk load-balancing to spray the load.
I never find Linux to suck, it's really depend on which architecture
it run, and what you want to do with it. You could quickly start a
small tomcat handling 50 concurrents users on recent ia32 boxes, multiply the number of boxes when the load increase, and use software
load-balancing/fault-tolerance features of JK to make the tomcat/linux
farm works well better than high-end (and pricy Unix workstations).
With a very good performance/buck ratio ;)
--
To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>
