Vincent Stoessel wrote: > Your recipe is interesting and I will look into it. From what I > understand about the nature of apache 1.3.x is that apache child > processes are not well suited to persist with mysql threads. For > example, if you create a php page with 3 mysql_pconnect() that > have different username or dbname parameters , then the child > server will make connection to a _new_ mysql thread, dropping the > old one.
IIRC, it will allow a maximum amount of pconnects per handler. But not just one, I think. Midgard doesn't do this -- it opens a connection, and keeps it open until the handler exits. > On the mysql end of things, it will keep the old threads > running and idle for up to 8 hours (28800 secs is the default config). > Linux+mysql must allocate memory for every open thread. So I have seen > cases of mysql server with very high load averages and high memory > usage. 85% of the cases have been solved by reducing the "idle_timeout" > amount to seconds instead of (8) hours and > using connect over pconnect destroys the thread immediately. This could well affect Midgard, since, as said, it does not close connections it doesn't (currently) use. If you use a sitegroups environment, you are most likely only using one, actively, though. Emile --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
