Rob, you rock.
Buffistas Building a Better Board
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
Go, Rob!
God, I love Buffistas.
Rob, wow. Go you!
With the continuous digging and the not despairing and the going-to-the-sources and, most of all, finding the origin of the problem!
Yeah Rob & Sergei!
If we can get the daemon restarted, and the problem goes away, do we still need to move?
Nice call, Rob.
If we can get the daemon restarted, and the problem goes away, do we still need to move?
If the daemon is restarted the error messages will go away, probably for a couple of months. If the current version of mysql is replaced with one that has these new patches applied, the error messages will go away permanently.
Whether or not we are using mysql too heavily is a separate issue.
It looks like we've been sharing one connection for forever. I'm sure the traffic has lightened and we may have lost posters due to lack of patience, but I can't see, under non-race conditions, how we'd honestly use more than 100, seeing as we're getting clumsily by.
I hate writing code that hits a bug in another system -- where the hell do you start to work around that?
At some point, the code should be rewritten so that mysql connections are preallocated, and kept open between page views.
This will signifigantly improve performance, since opening and closing msyql connections is a relatively expensive operation, especially on the server side.
If they are open between page views, how then can we have 101 simultaneous users?
Or do mean sharing connections between sessions? Is that possible?
I understand that the opening and closing is expensive (although were were told to explicitly close after every open as part of trying to minimise this error).
My gut reaction is that they should be open for a page, and no longer.
Well, hallelujah...
Bravo, Rob and Sergei!!!
Or do mean sharing connections between sessions? Is that possible?
Yes, and yes, using the mysql_pconnect function.
Persistent database connections.
It comes with this warning, though:
Using persistent connections can require a bit of tuning of your Apache and MySQL configurations to ensure that you do not exceed the number of connections allowed by MySQL.