If you want real results that you can show to your boss (God forbid), you should fire up multiple instances of your CGI (perhaps with
FastCGI. yes i realize i link to this site alot nowadays!). Then bombard your test server with CGI POSTs to the script. If you're expecting heavy usage of your CGI script, then you should really be using
mod_perl or FastCGI, anyway. You should test more than one process when you're testing a program since other factors can compromise your results. Testing the program at maximum load could possibly reveal a weak spot or breaking point, especially if their are databases, file ~locking, or IPC invloved. The best way to test, is to put it under heavy fire. You could use
Benchmark to test specific regions or algorithms in your code for possible improvement. Give it a whorl and post what you get in the
Code section. Have a nice day!
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.