The question is: where is the bottleneck?

There is no point trying to "throw" optimizations at the problem if you don't know where the problem is. Changing your forking model or your schema or your queries won't help if that isn't where the problem lies.

So, my suggestion is to profile your code; find out where in your process large amounts of time are being taken. Then fix those areas or post back with the specifics looking for particular optimizations.

It may seem like a lot of work (possibly not-fun work) trying to determine the bottlenecks. But it sure beats reworking a whack of code only to find that the particular problem is not solved.

In reply to Re: Database poller by mobiGeek
in thread Database poller by Marcello

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.