Those bugs don't cause any extra resource usage. They just cause the count of open connections to be incorrect.
I don't know of any bugs in MySQL that cause the board to consume extra resources.
Host ,'Why We Fight'
A thread to discuss naming threads, board policy, new thread suggestions, and anything else that has to do with board administration and maintenance. Guaranteed to include lively debate and polls. Natter discouraged, but not deleted.
Current Stompy Feet: ita, Jon B, DXMachina, P.M. Marcontell, Liese S., amych
Those bugs don't cause any extra resource usage. They just cause the count of open connections to be incorrect.
I don't know of any bugs in MySQL that cause the board to consume extra resources.
Those bugs don't cause any extra resource usage. They just cause the count of open connections to be incorrect.
Well, money is a resource, and all of our shared servers charged us for the miscounts.
Rob, were you the one working on MARCIE?
I don't know of any bugs in MySQL that cause the board to consume extra resources.
Hmm. Odd. The previous host correlated the incidences of us eating every connection with the CPU usage spiking and bringing server performance to its knees.
You're saying there's something else we should be looking at in our code? Did you notice anything while you were working on the filter?
As a webhost, I can say, without question, that a connection is considered a resource.
We were spiking the CPU, weren't we, Kristen? At the same time as eating all the connections, which is why we were capped and the code rapidly became useless and we left?
Yes, you were. I need an analogy. Gimme a minute.
I've gone to the analogy well and the well is dry.
Basically, yes, connecting to the database uses server resources. Querying the database also uses server resources but not nearly as much. Which is why connections and MySQL usage are so closely monitored and can get you TOSed out on your ass.
Rob, were you the one working on MARCIE?
I was, but I'm not anymore. Where I left it was pretty much working, but with one bug that I couldn't figure out. ita has the details of what's happened since then.
You're saying there's something else we should be looking at in our code? Did you notice anything while you were working on the filter?
I don't know how to optimize PHP/MySQL applications, but if there's someone who does, they should have an easy time modifying the code to be more efficient. It's well structured and well documented, which makes modification much easier.