WordPress 2.1 Release Candidate 1

WordPress 2.1 Release Candidate 1 is out. Ryan Boren has the details over on his blog. There’s a list of changes in 2.1 at the WordPress codex, as well as a list of plugins that are compatible with WordPress 2.1.

If you’re using WordPress 2.1 RC1, you can give feedback via the testers mailing list or at the forum for beta releases.

The WordPress developers are already thinking about WordPress 2.2. With 2.2 they’re gonna start doing time based releases, trying to release every four months:

With 2.2 we’re going to start doing time based releases. We’re going to try to do a release every four months and limit the scope of the changes to what we can realistically achieve within that timeframe. The goal is to get cool new features into user’s hands more often instead of saving them up for the one big release every year.

WordPress 2.1 MySQL Requirements

Ryan Boren posted about MySQL requirements in the upcoming WordPress 2.1 release. WordPress 2.1 will require MySQL 4.0, MySQL 4.1 won’t be required until WordPress 2.2 comes around. So, WordPress 2.1 will require at least MySQL 4.0 to function correctly. No more MySQL 3 people. If you’re still using MySQL 3, it’s far past time to upgrade.

MySQL AB discontinued support for MySQL 4.0 back in September, so it’s likely hosting companies will be upgrading to 4.1 within a year or so.

Also, WordPress 2.1 beta 3 is out, it’s running on this blog right now.

Moving Servers At Dreamhost

After making this post, I submitted a support ticket to Dreamhost. Justin at Dreamhost replied back with a pretty solid sounding solution:

I did notice a few busy sites on the apaches for 2 of your domains. I started a move to another IP/apache which should complete in a few hours, and we can see if that apache turns out to be more stable. Since the server-status page for the old 2 showed an uptime of about 1 hour, likely the sites were causing that apache instance to time out and need to be restarted, resulting in a bit of downtime. Give it a try for a day and if you still have problems, let me know!

Perfect. Switch my domains over to a new httpd process with less activity. Makes sense. Well, after that was done, not much of an improvement was seen, as you can probably tell.

Today, I received another email from Justin saying he noticed longren.org was still slow to respond. He offered to move me to another server, assuming I was willing to have some downtime. He even asked if there was a time I’d prefer the move to be made. I asked him if 10:00 PST would work, and it did. So, this site is going to be offline for a few hours tonight while it’s being moved to a new server. The actual switch won’t take very long, I’ll just have to wait a few hours for the DNS to start pointing to the new IP.

Hopefully everything will be up and running along nice and smoothly tomorrow morning. Also, Justin at Dreamhost is awesome. He’s been very attentive and always offers possible solutions. Thanks again Justin!

Horrible Repsonse Time

longrenOrgEvenSlowerLongren.org has been really, really slow the last week or so. This site has never been this slow to load, even when I was hosting it out of my house on my cable connection. Granted, I didn’t get the traffic back then that I do now, it still shouldn’t be this slow.

Last time longren.org was being slow as shit, I posted an image of a graph from Site24x7, like I’ve done in this post. The response time in the earlier image is horrible, 4510 ms, but that’s a lot lower than I’m seeing now. As you can see from the image above in this post, the current average response time over the last 7 days is 6614 ms.

This has to be a result of something going on at Dreamhost. I say that because sometimes pages on longren.org will load up in a snap. Most of the time though they take between 15 and 30 seconds to load. Even sending queries to the database is slower than normal. Database queries are usually done being executed within 1 or 2 seconds. Lately, it’s been taking 5 to 9 seconds. Something is definitely up. Perhaps I will submit a support ticket to Dreamhost tomorrow. Yay.

A Cake For Firefox

Cake For FirefoxFirefox recently released Firefox 2.0. There was a little slip-up with that release though, it hit some FTP servers earlier than it should have.

Anyway, the Internet Explorer team at Microsoft sent a cake to the Firefox team, congratulating them on their release of Firefox 2.0. Pretty weird huh? One would expect the cake to be full of poison, but that’s not the case. It’s simply a “job well done” present from the IE dev team to the Firefox guys.

It’s nice to see archenemies sending such nice gifts, even if it is Microsoft that’s involved. Can you feel the love?