Hey, I think Dmitry has some valid points. When I used Jmeter for one of retail projects, the focus was more on loading the server. It was all about the server gettting bombarded with requests and it responding back.
Plus, I had to maintain the cpu of the load simulating machines well below 50% to make sure that the load simulated is actually happened at the server. Meaning, had to keep the response processing as low as possible. Regards Subrahmanya A On 10/25/07, Dmitry Kudrenko <[EMAIL PROTECTED]> wrote: > > > MG> Now my questions: > MG> - does JMeter's architecture allow to plug something like WebTest or > MG> HtmlUnit as "execution engine"? > MG> - is there interest in JMeter community for such a combination? > I am using JMeter and CanooWebTests. > > But as for me, there are rather different aims for performance testing > tool and for functional testing tool. > > When you are testing performance you should send requests as quickly > as possible. You don't need to spend time for parsing html, supporting > javaScript, building DOM, etc… > > You should send requests for loading server. As for AJAX: It is > possible to test AJAX applications, you don't need support > HttpXmlRequest for this. Just send request and process the response. > You need to implement your web client logic on JMeter plan. It is not > very easy, but it is possible. > > Another problem when you want to test application and client should > send several requests in the separate threads using one session (to > test AJAX really asynchronous)... But I think it is another theme for > discussion. > > -- > Best regards, > Dmitry Kudrenko > ARDAS group http://ardas.dp.ua > mailto:[EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
