Update 2:: Still had some trouble getting the site up, and then I had to leave because my daughter was getting five teeth pulled. Sorry, she takes priority over y'all.
So I restarted the server, but I may have to bounce it a couple more times before it's running smoothly again.
Update: No sooner did I post the following than our ISP shut down our server, for some reason. So we were down for five hours over night because of my stuff, then we were down an additional three hours because of our ISP. ISP says it was a "kernel failure". OK, whatever...
I also got a (bogus) $250 parking ticket from an AC Transit cop yesterday. If the A's hadn't won last night, I'm not sure how many things there'd be around my house that weren't smashed.
Well, the upgrade took me a heck of a lot longer than I thought it would. One of these days, I'm gonna pay for a development environment that's identical to the production one, so I can figure these problems out before it affects y'all. Perhaps after we get some revenues coming in...
I was trying to do two things:
Remove some database indexes that didn't look like they were being used (which slowed down inserting new data, such as comments)
Switch over from a non-threaded Apache server to a threaded one, to see if that would help speed things up.
Seems that you can't just drop an index in MySql and forget about it. MySql then wants to rebuild all the indexes on that table. That took a while, about 10 minutes per index.
Then when I upgraded the Apache server, mod_perl wasn't happy anymore. So I had to recompile it, and reinstall it, and that broke some code. So I had to fix the code to work with the new version of mod_perl.
Then when all that was over, it seems that I needed one of those dropped indexes after all, because the site was slower than ever. So I had to figure out which of those indexes I dropped was the one I still needed with some step-by-step debugging. So I had to recreate that index again, which meant rebuilding all the indexes on that table, which again took time.
I finally got the site working at about 4:30am. But then it seemed a little unstable, so I backed out the threaded version, and went back to the non-threaded server, because I need some sleep.
So if the site seems slow or has a bug or two, I'll fix it when I wake up. Perhaps I should set my alarm for the A's game at 12:35...