Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

Re: Re: Sharing database handle

by graff (Chancellor)
on Apr 20, 2002 at 00:40 UTC ( #160713=note: print w/ replies, xml ) Need Help??


in reply to Re: Sharing database handle
in thread Sharing database handle

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.


Comment on Re: Re: Sharing database handle

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://160713]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others rifling through the Monastery: (6)
As of 2014-12-27 23:50 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (177 votes), past polls