Those evil gremlins are starting to look pretty suspicious!
DB lock is of course now completely out of the question as is poor disk performance. That I isolated weeks ago.

I don't know about the mechanics of the interaction between Perl and Apache, but is certainly perplexing why (given that it is a network issue) a client could hold back the successful execution of a cgi script. The internet would effectively grind to a halt if that were the case.

I've read that Apache no longer buffers perl output since V1.2, leaving the Perl buffer as the only bottleneck, and like I said, $| = 1; and $| = 0; make no difference!

In reply to Re^2: CGI print statements taking forever by traxlog
in thread CGI print statements taking forever by traxlog

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.