It looks like you're using an Ad Blocker.
Please white-list or disable AboveTopSecret.com in your ad-blocking tool.
Thank you.
Some features of ATS will be disabled while you continue to use an ad-blocker.
By that description, I'm fairly certain something was broke.
Originally posted by SkepticOverlord
The short version of the long and painful story...
It had been a while since I optimized the database, and after a long list of code improvements (fewer overall queries and more efficient queries), it seemed time to do it. While I was initially kicking myself for "fixing what ain't broke", it turned out that the process uncovered serious issues with the database and our backups... combined with an improper initial OS configuration for very-large databases, repair and recovery took some time.
And now the painful realization that we've outgrown yet-again another server. We're looking at solutions (expensive) to migrate to faster/better database hardware than a server with dual Dual-Core 2.3 GHz Opterons, 8GB ram, and 10k RPM drives in a RAID.
Originally posted by TheAvenger
Are there any confirmed overnight cases of A.T.S. posting withdrawal syndrome?
Originally posted by jsobecky
There have been reports of large numbers of people wandering aimlessly outside, looking up at the sky and mumbling about a large. bright, yellowish orb that is suspended up there.
Originally posted by supercheetah
By that description, I'm fairly certain something was broke.
Originally posted by TheAvenger
Are there any confirmed overnight cases of A.T.S. posting withdrawal syndrome?
Are those backups for replication? Do you use any backup servers as read-only for load-balancing, and update from a master? Or is it all really just for backups? How about table partitioning? Is there any possibility of that?
Originally posted by SkepticOverlord
Originally posted by supercheetah
By that description, I'm fairly certain something was broke.
We found out the hard way that the vendor did set up the server to spec (we've had it about 9 months)... one of the main problems was the tmp volume was way too small, introducing a littany of issues for a big MySQL installation.
And all of the code developed over the past 3 weeks was designed specifically to use fewer queries, and simplify remaining queries (still some to run through). We now use about 60% fewer queries than typical PHP-based boards. But since we regularly encounter more than 50,000 visits a day (mostly from guests), that's very-high traffic for any board. So our issue is the load the traffic causes on the db hardware.
Originally posted by enjoies05
I'm not sure but I did sit there for a good 20 minutes clicking the refresh button waiting for the "Under Maintenance" screen to go away.
Originally posted by enjoies05
I'm not sure but I did sit there for a good 20 minutes clicking the refresh button waiting for the "Under Maintenance" screen to go away.