build a model like - each user is on the site for n Minutes - each user makes n requests - the mean time between to page requests is n seconds - each page request creates n http requests - specify the average size for an http request - specify the average ratio of request/db access
......... With that you can compute memory usage, requests/per second, concurrent databae connection etc. With these number you have to test your application (not tomcat) and see what your application can handle. There is no rule of thumb. (It can't be, it's like predicting the time to ride by horse fom New York to Frisko, whithout knowing the rider, the baggage and without having a map) Depending on the structure of the site and the effort you want to invest you can improve the result by building groups of users, pages, requests and estimate these. > -----Original Message----- > From: Heart Prince [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 05, 2003 2:57 PM > To: [EMAIL PROTECTED] > Subject: how to suppor 30000 concurrent users > > > howmany concurrent users does tomcat support? if i want to > design a web > application for 30,000 concurrent users, what is the step? > clustering is > related to this? how many servers i need if i am clustering > > _________________________________________________________________ > Latest movie trailers. On your mobile. > http://server1.msn.co.in/sp03/gprs/howcani_movie.asp With GPRS. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
