Hello:

I spent all morning benchmarking my script on a costumer's site to see if they could be some unecessary server load.

To do this test I used the Benchmark module. I tested all my CGI's and saved their benchmark outputs on different tasks.

This tests took me to a question I've never asked myself before, "What should be the optimal CPU usage for a script?", I tried to search for some posts like this but without success, so I decided to make a post here.

Here are different CPU usages I had from my CGI's: 

/apromo/apromo.cgi - 0.06 CPU
/baboon/myMail.cgi - 0.15 CPU
/baboon/entrada.cgi - 0.14 CPU

[download]
I hope someone could guide me or give me some links where I can read about this.

The main goal is to know if my CGI's are efficient enough or if I could get them to be more efficient.

THANKS

In reply to Benchmarking Tests by kidd

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.