OK, the time has finally come... we have a new server!
I will be spending tonight and all day tomorrow transitioning to the new digs... I don't expect it to affect us until late tomorrow afternoon.
I will make give everybody a warning then take us offline for (hopefully!) 3-4 hours...
When we are done, we will have a new home with 6 TIMES the power and RAM as before... I expect to see some MAJOR upgrades in performance... once we have settled into the new server, I will start to prep us for a major upgrade to our Vbulletin software... but that may wait until the post season...
I know it's been a long time coming, but bear with me for a little longer and it will all be worth it! [Reply]
Found an interesting bottleneck and tried an experiment that seems to have helped (converting the session table from MEMORY to InnoDB). Seems like a bad idea, but things got better instantly, so...we'll see. [Reply]
Originally Posted by DaFace:
Found an interesting bottleneck and tried an experiment that seems to have helped (converting the session table from MEMORY to InnoDB). Seems like a bad idea, but things got better instantly, so...we'll see.
Does seem quicker.
You the man face
Sunday is double time, too! [Reply]
Originally Posted by limested:
Any of the tables that are constant write to should be converted to InnoDB. If they are primary read only tables the MyISAM.
I get that for most tables, but the session table is almost universally believed to be best as a MEMORY table. But I did some reading that suggested InnoDB might be better for relatively high-use servers, and we basically have the whole DB read into RAM at this point anyway, so I figured I'd give it a go.
I don't fully understand WHY it worked, but it certainly seems to be making a difference. The backups are still doing their thing in the background, and our CPU load is a little elevated, but I'm hopeful that we're chipping away at the various bottlenecks.
FWIW, AC told me that PHP 7.1 is on the radar (which requires a slight update to vB 3.8.11 as well). The rest of the stuff is up to date at this point. [Reply]