If you’re reading this message, then you’ve connected to our new, Windows Azure-hosted server instance.
Through December 1st, we’ll still be experimenting with performance-enhancement options. If you run into anything odd, and it persists for more than an hour, please leave a comment here. Or, if you’re unable to do so, send an email to [email protected] (you should know the domain name to use since you’re on this site).
One thing to keep a close eye on: we’ve enabled some DNS-based security via CloudFlare. With our old server, this periodically went awry and would display a “site not available” error from CloudFlare. We’re trying it again, but we’re prepared to turn it off if it’s wacky. Often, reloading the page clears the error, but we’d like to know if it’s happening.
As it stands, we’ve gotten page load times for a typical forums discussion page (pretty much our worst-case scenario) down to under one second, with Page Speed and YSlow scores of over 90%. Based on load testing, we should be able to maintain good response times even under more than double our typical user load.
- The process of taking the site data from a database, into text files, and back into a database invariably results in some off characters cropping up here and there, especially where the original content contained special characters like “em dashes,” curly quotes, and so on. We’re making an effort to fix these in articles and permanent pages, but will not be doing so in the forums.
- If you posted new content (such as a forums question or response) late Wednesday night (November 27th), that content may have been lost in the migration. There was a bit of a problem with the backup and cutover process, and we apologize for any inconvenience.
Potential issues to be on the lookout for: