Signed up for a patron membership to help this board with its funding needs. Where did the money go? Doesn't seem to be improving the reliability of the server.

 

for them to buy more porn memberships

 

+1

 

No shit. And I paid for a full year membership. WTF is up with that?

 

Would some admins please chime in here, if they only solution is a better server could we get a ball park figure of how much its going to cost, im sure many people on Driven would donate money including myself if we were sure it wasnt going to waste.

 

The problem is not a server as I've told Sung several times that I'd buy the server myself, just that I want to have it hosted somewhere locally.

As of yet he hasn't contacted Cox regarding hosting, or investigated any local co-location facilities. If you want to help, try those avenues, i.e. a facility to put the server and not a server itself

 

The owner of www.Corral.net (which has much higher traffic) has a T1 to his house and runs it out of a spare bedroom. Cost is about $700/mo for the Central VA area for a dedicated residential T1 line if I recall correctly. Not sure what it is in the NoVa or 757. That's the way to go.

 

For the database issues, try splitting Eye Candy and Classifieds into seaparate databases from the rest of the forum. Those high traffic areas could easily be migrated over and use the same user logins. Searches would be the only affected area since searches would not go across the databases by default. This would be a good thing.

 

Seeing as how we only have one server this really wouldn't help much aside from the reduced search functionality. If we had multiple servers to make a database cluster maybe this would make sense. We'd disable searches on certain forums before we tried to split the database up.

I suspect the issue is Apache and/or MySQL going bezerk and chewing up all the memory resulting in swapping to disk, but as of yet no one has been able to isolate the cause of the slowdowns when they happen.

 

MySQL may be trying to reindex itself, can you check those settings?

For the MyISAM, try "--delay-key-write=ALL" and "--myisam-recover" options. If not set correctly, that could explain disk thrash during a crash.