Yeah, he mean threads as in the technical term, which is like one instance of a program running -- the details are a) not so important and b) going to be badly explained by me, so never mind.
However, the tech guy says it's connections, not threads, so we need to focus on addressing what he sees as the problem. He calls the shots.
edit: Or what Rob said.
Is it total number of connections over a period, or max concurrent connections that they are concerned about?
I think it's the # of connections open at that "moment", but I'll double check.
Yup, as I recall it was max concurrent connections that are the deal.
Do we know when they changed the wait_timeout from the default to five minutes? Was that after the last time the server fell over and caught fire?
They are now. There was a problem with a link in erika's post. It's fixed.
On the message center refresh, the message is showing MIN_RELOAD_TIME text instead of the actual minimum number.
Stupid lo-pri question: how hard would it be to put a live link back to the message center at the end of every threadsuck?