|
Jason,
We use a combination of Tomcat and Apache. However, if you do not have much static content, then standalone Tomcat would work as well. I have also heard good things about Resin. In terms of JDK, I would recommend Sun's JDK because we have had support issues with IBM's JDK. There are a number of factors which impact how much a single server can support; e.g., nature of the application, frequency of the hits, etc. I was surprised by your numbers and would expect the numbers to be much higher. How was your benchmark done? Cynthia Jeness
"Jason R. Kretzer" wrote: Hello all: I have been put in charge of testing various configurations to determine which has the most efficient use of CPU time and which can support the most users. Note we have a shoestring budget for this. I am new to the servlet game so this is what I have to work with right now. WHAT IS GOING TO HAPPEN:Clients connect to our servers and run a java application via servlets. DIFFERENT CONFIGURATIONS:(which is more efficient?)Servers:Tomcat(alone)Tomcat(with Apache)Apache(with Resin)Any other free/cheap ones you may suggest. We only need to be able to run servlets. Operating Systems:Win 2k serverSome Linux distro JRE:IBMSunOthers? We have done some preliminary testing and found that a server with a 1.4GHz and 1GB ram can only handle about 10-15 users. Is this about right? Or should it be higher? We are hoping for up to 40 or 50 and maybe even 100. Also, we are looking for some server stress testing software for simulating many users trying the server. Again, we are trying to operate on a smallish budget. Any help you guys/gals could provide would be appreciated. Thanks, -Jason |