Not specifically, but I've dug all over the place. Trust me, if it was something I could figure out by digging around and trying shit, I would have. I probably wasted 40-60 hours screwing with the damn thing during a two-week period a while back.

I feel like Bill Paxton's character in True Lies.

+1

Cheap bastard.

Holy shit..lol..well, like it hasnt been said eleventy billion times already. thanks for everything you do! I know the pay isnt as good as it was when you were an employee of RainMan Inc LTD ™ :evil:

it is probably an optimization issue in MYSQL, That would be the place I would start looking first.

I take that back because I rarely see a database error message when the site is having issues, lemme think a few minutes....

This place has a massive ****ed up database ;) and MYSQL is a ****ing pain in the ass. when you dont allow guests it runs like a champion.

I just donated $10 with the stipulation that I'll donate more if a Donation Request thread is created for a new server...

I notice the site hangs, wonder if you may have a bad stick of ram or possibly a hard drive failure in the early stages?

Well, actually unless they have a very old server, it should handle a thousand or so on at once with some slowdown but not crashing... I had over 750 online at once on my server.. and it barely got over a 2 on the server load

I know at peak times, especially after a loss this place is hard to get on but during the week this should not be happening... Still think it may be a bad stick of ram or a hard drive beginning to stick and fail

Eh, maybe, but I doubt it. The basic underlying condition is that we occasionally have a query that just gets "stuck." Many times, it's a completely innocuous query (like the one that grabs the posts for a thread), so it's not that the specific query is the issue. But when one gets stuck, it locks the POST table, which causes tons of others to back up behind it.

Most of the time, the stuck query eventually finishes up, and the rest then complete. That's what is happening when we have a 15-30 second lag here and there.

Other times, the query just gets stuck for an insane amount of time. They're supposed to time out after a few minutes, but often don't for some reason. When that happens, it can take the place down for a long time until MySQL eventually croaks and resets itself. By that point, the stuck query has driven our server loads through the roof, so it takes even longer for the average load to come back down far enough for vB to let people back in. That's generally the issue we've seen on gamedays.

I THINK it has something to do with our memory allocation (key_buffers and stuff like that), but my tweaks don't seem to make any difference.

Our POST table is over 2 gigs in size - that's much more of a likely culprit than heavy user load. I've added a couple indexes, but that obviously hasn't helped much.

You dont restart MYSQL when it lags? it's an automated reset?

If I'm around, I do. If not, it hangs until mysql crashes and restarts itself.