Thanks a lot for the information. It is very useful, as we are rather new to web testing, and are still debating what methodology and tools to use. Your insights will help us make decisions.
Thanks again, Veronica ----- Original Message ----- From: "peter lin" <[EMAIL PROTECTED]> To: "JMeter Users List" <[EMAIL PROTECTED]> Sent: Wednesday, October 29, 2003 6:20 PM Subject: Re: high-load remote testing > > On my gateway 450X laptop, I can simulate 7-8K requests per minute for a static HTML page. From personal experience, very few sites can generate that kind of traffic. My laptop is 1.4ghz and both tomcat and jmeter were running on the same laptop. > > You should be able to simulate 1700/req second if you have two ethernet cards per system and use 10-12 systems. In the past, before I started using JMeter, we simply got 5 guys together on a friday night to run the test. > > What we did was have each person start the test on two systems and used a total of 10 systems. At that time we were using Weblogic 5 and it pretty much maxed out around 100 req/second on a Sun T1 rackmount server. > > Unless the server your hitting has 4 or more ethernet cards and tons of processing power, you'll probably kill the server long before it reaches 500/req second. > > Keep in mind that kind of traffic requires multiple T3 connections. An article I wrote on performance is posted on Tomcat. http://jakarta.apache.org/tomcat/resources.html > > peter > > > > > Veronica Baiceanu <[EMAIL PROTECTED]> wrote: > Hi, > > Our company will stress-test a commercial web application, and we are targeting a rate of 1700 hits/second on the application server. We are currently estimating whether we can use JMeter to achieve our goal. So far, I have tried JMeter remote testing using 2 remote JMeter servers, and one controller. I haven't encountered major problems with this setup. However, it would help me to know if anybody successfully used JMeter for achieving a throughput comparable to the one we have in mind. > > > > It would be particularly helpful to me to get some insights regarding the following issues: > > > > - I read that the controller can become a bottleneck in remote testing. Several suggestions were made to solve this problem. The ultimate solution would be giving up remote testing altogether. Instead, each test would be launched by hand from each machine, the times should be coordinated, the results gathered in CSV files, and then merged to get the overall results. I believe I might need at least 5 JMeter servers to get my workload, possibly even 10. I would rather use the remote setup. I wonder if anybody managed to run JMeter in the remote setup, with so many machines, and with my targeted workload. > > > > - It would be helpful if I could get any recommendations regarding the hardware I should use for the testing, i.e. the minimum indicated CPU speed and memory capacity for the machines. We could get 5-10 decent machines that we could dedicate to testing. I wonder if the JMeter resource consumption for large-scale tests could become so critical, that JMeter simply cannot be used. I would not expect the CPU consumption to be higher than for test tools written in C, but the memory consumption should clearly be higher. Any information about particular setups you used would be greatly appreciated. > > > > Thanks a lot, > > Veronica > > > > > --------------------------------- > Do you Yahoo!? > Exclusive Video Premiere - Britney Spears --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
