Okay here is detailed results:



Code Time=0.0715248584747314 seconds

Start Code Execution=1217024869.1958

End Code Execution=1217024869.2

LWP Start Time=1217024848.42043

LWP End Time=1217024871.99951

LWP Total Time=23.5790810585022

LWP Start->Code Start=20.77537 seconds

Code End->LWP End=2.79951 seconds

Head Time=20.0828440189362 seconds

Total LWP Time For Google: 1.80555105209351 seconds

Margin Of Error For LWP<->Code results: around 2 seconds

so by the look of this...it took 20 seconds just to start up the code...since the code though is in PerlEX/Mod_Perl it shouldn't take this long..so either server is taking logn time to start up...or ModPerl and PerlEX are loosing their cache/taking long time to access the cache?
Anyone have any ideas on what to do now?

In reply to Re^2: Timing concerns on PerlEX/Mod_Perl by Anonymous Monk
in thread Timing concerns on PerlEX/Mod_Perl by Anonymous Monk

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.