Chris:
I wouldn't count chickens before they hatch, but the hatchin's looking pretty good so far.
There were many things that were done (and many issues found) since the quest/diagnosis began. The forum speed problems were actually an "onion" whose skin we had to peel back, layer by layer.
There *were* some significant network connectivity issues in the beginning -- obvious speed/duplex mismatch problems between the AZB server and the network switch ports it was connecting to -- which we had to work with a third-party network operations center to resolve (we didnt have visibility or control over the network switch).
Then there was a SIGNIFICANT reverse DNS resolution issue (IP Address -> fully-qualified domain name) whereby, again, we had to work with the third-party to resolve, as well as put a workaround in ourselves (i.e. standing up our own DNS service and pointing the AZB server to itself for DNS).
All through this, Mike H. was working on the database end, optimizing things, etc. We noticed then, after remediating the network connectivity and DNS issues, that there was another layer to the onion. Whereas before the speed issues were constant, this time, they were inconsistent (i.e. it would be slow, and then suddenly speed up again).
This last thing done was a hardware upgrade, to make sure the database was on the fastest hard drive technology possible -- to make sure the database queue can get serviced and purged as fast (as possible, anyway) as requests coming in.
Know this -- we're not done yet, and work is ongoing. There are some further upgrades planned in the future.
-Sean