I recommend you play with jarkarta JMeter to have informations about your response time depending on load, simulteanous request served and so on. It's difficult to tell you the behaviour of tomcat with maxprocessors at 500, this mainly depend on the os, the server, the bandwidth and the response time of the webapplication running inside tomcat. All tomcat does is dispatch incoming request to webapplication after a small amount of preprocessing.
Increasing the maxProcessor could lead to more context switching by os (which takes time) which will increase the response time for a request, which mean a processor will be used for more time, which mean (if you assume stable incoming requests rate) more processors needed at the same time which will need more thread, which will stabilize at some point overall decreasing your quality of service. On the other hand, reducing processors could lead to people waiting longer on the processors queue, reducing response time and reducing quality of service. There is an optiumum you need to find experimentally :) En l'instant précis du 08/03/07 15:00, Leon van der Merwe s'exprimait en ces termes: > Hi guys > > I need to know what the max is that I can set my connections to. > > We are running the app of the server that is robust. > > Want to up it to about maxProcessors from 75 to 500? > > Thanks > > Leon van der Merwe > > FinSource > > FinSource (Pty) Ltd > 22 Leeuwen Street, Cape Town, 8001 > PO Box 3149, Cape Town, 8000 > > Tel: +27 (0)21 480 8600 > Direct Line: +27 (0)21 480 8710 > Fax: +27 (0)21 480 8700 > [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > www.finsourcegroup.com <http://www.finsourcegroup.com/> > > A Maitland group company > > BVI Cape Town Dublin Durban Geneva Isle of Man Johannesburg > London Luxembourg Monaco Paris > > ************************************************************************ > ************************************************************** > This e-mail is confidential and may also be privileged. If you are not > the intended recipient, please delete from your system and notify the > sender now; you may not use, disclose, distribute or copy it. Anyone > who communicates with us by e-mail is taken to accept the risks in so > doing. E-mails are subject to data corruption, delay, interception and > unauthorised amendment. Nothing in the message is capable of or > intended to create any legally binding obligation and it is not intended > to provide legal advice. > ************************************************************************ > ************************************************************** > > > > > > > > ##################################################################################### > This e-mail message has been scanned for Viruses and Content and cleared > by FinSource Infrastructure Services' MailMarshal > ##################################################################################### > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
