|Another option maybe for the child processes not to write to the database at all (especially in the case with
logging) and for the parent to dump the data into the db at regular intervals.
Well, this may be an option, but it's probably not a good
idea. You'd hate to have a bunch of inserts or updates
queued in the parent and then have that process
go down before it can finish the queue, or find out that
the connection dropped for whatever reason since the last
time it processed a queue.
Has anyone (esp. Marcello) seen data about how much it costs
loadwise to have a bunch of child connections? My own
(anecdotal, not systematic) experience has been that the
number of connections is less important than what those
connections are doing. If the SQL demands of any one
process are heavy, having more than a couple going at once
will hurt, no matter how you do it. If it's easy stuff, then
number of concurrent requests is not much of an issue.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||