C
Charlie
Hi folks,
I am working on the Web application testing these days, and I have
some questions need to clear.
Basically the application that I am testing is using the
Apache/cgi-bin, the back end database is mysql. From user point of
view, it is a website where you can place several "business" Orders.
The way that I am doing the testing is also by using the
Apache/cgi-bin( a seperate Apache running on different platform),
basides, I have used a list of modules get from www.cpan.org, such as
WWW.Mechanize, Threads, etc. I have created my perl file to simulate
realtime users' interaction, filling the text area, picking the radio
box, etc, till at last to push the submit button to have the order
submitted.
What I really interested is once the final submition button is pushed,
when the confirmation page is desplayed to the uses, (in
Perl/Mechanize, when "mech->submit()" is finished), while there are
tens, houdreds users doing the same thing concurrently.
So far I have created some testcases to test two kinds of orders. The
first one takes about 20 mi-seconds for that period of time, while the
second one takes about 20,000 mi-seconds. To create those two kinds of
orders, it may needs some extra informations for the second one than
the first one.
So based on the above description, can I necessarily say that the
performance of the second one is not as good as the first one ???
Do you see any overhead on this test module? the time consumed by the
Apache, perl/cgi-bin, not consumed by the real transaction ?
thanks a lot for any tips
CJ
I am working on the Web application testing these days, and I have
some questions need to clear.
Basically the application that I am testing is using the
Apache/cgi-bin, the back end database is mysql. From user point of
view, it is a website where you can place several "business" Orders.
The way that I am doing the testing is also by using the
Apache/cgi-bin( a seperate Apache running on different platform),
basides, I have used a list of modules get from www.cpan.org, such as
WWW.Mechanize, Threads, etc. I have created my perl file to simulate
realtime users' interaction, filling the text area, picking the radio
box, etc, till at last to push the submit button to have the order
submitted.
What I really interested is once the final submition button is pushed,
when the confirmation page is desplayed to the uses, (in
Perl/Mechanize, when "mech->submit()" is finished), while there are
tens, houdreds users doing the same thing concurrently.
So far I have created some testcases to test two kinds of orders. The
first one takes about 20 mi-seconds for that period of time, while the
second one takes about 20,000 mi-seconds. To create those two kinds of
orders, it may needs some extra informations for the second one than
the first one.
So based on the above description, can I necessarily say that the
performance of the second one is not as good as the first one ???
Do you see any overhead on this test module? the time consumed by the
Apache, perl/cgi-bin, not consumed by the real transaction ?
thanks a lot for any tips
CJ