Howdy, Not a problem, good luck, have a good weekend, be cogent, and keep us updated on how it goes ;)
Yoav Shapira Millennium ChemInformatics >-----Original Message----- >From: Dale, Matt [mailto:[EMAIL PROTECTED] >Sent: Friday, December 19, 2003 10:40 AM >To: Tomcat Users List >Subject: RE: architecture advice > >Thanks, > >I think I'll take your advice, the apps guys are going to use J-Meter for >app testing so I'll get them to use this for stress testing as well. > >Thanks for clearing up my misunderstanding, it came from my observations >but they were hardly conclusive. > >Thanks >Matt > >-----Original Message----- >From: Shapira, Yoav [mailto:[EMAIL PROTECTED] >Sent: 19 December 2003 15:26 >To: Tomcat Users List >Subject: RE: architecture advice > > > >Howdy, > >>I currently have a 6 processor Solaris box that we wish to turn into a >>tomcat application server for 250-500 users. >>My current plan would be to run two instances of tomcat 5 in a cluster >with >the session replication enabled and load balance between these two >using >the JK2 connector from apache 2. > >It's good to have a goal and plan in mind. Make sure to establish the >acceptable response time for a page in your application when handling >the maximum expected load. This is what you will test for. > >That said, why not start simple? Configure just one standalone tomcat, >deploy to it, stress-test and tune it. Then worry about clustering and >failover. > >>Would I be better having 1 tomcat instance and allowing it to take more >>memory? (I decided against this as surely each instance can only >utilise a >single processor) > >That's not true: the JVM can effectively utilize multiple processors >concurrently. We have several 12- and 18-processor Solaris boxes and >Sun JDK 1.4.2 parallelizes beautifully on them. Be careful jumping into >conclusions like the above without researching/testing. > >Yoav Shapira > > > >This e-mail, including any attachments, is a confidential business >communication, and may contain information that is confidential, >proprietary and/or privileged. This e-mail is intended only for the >individual(s) to whom it is addressed, and may not be saved, copied, >printed, disclosed or used by anyone else. If you are not the(an) intended >recipient, please immediately delete this e-mail from your computer system >and notify the sender. Thank you. > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
