Archive for December, 2007

Blog Performance Improvements

Saturday, December 15th, 2007

As many “first responder” Scot’s Newsletter subscribers found out when the last newsletter went out on December 6, access to the database that underpins the Scot’s Newsletter Blog is limited to 50 simultaneous database calls by my webhost. Every shared webhost that I’ve come across has a similar MySQL access limit. So the limit was no surprise.

But I was not expecting so many readers to be unable to read any of the stories at all, or to have to wait “minutes” for pages to load, during the first couple of hours after the newsletter mailed. Normally, the blog is very fast, snappy even. So the problems that many people saw were temporary. But I experienced the slow performance myself. Even though the problem lasted only about two hours until peak demand wound down, the experience for the people who respond right away to the newsletter is unacceptable.

In case you’re wondering why this happened, there are some underlying technical issues that I’ll come back to shortly, but the primary cause is that the change to a blog focus means that the newsletter no longer contains whole articles; it describes articles and links to them on the blog site. Everyone who reads a blog post by clicking a link in the newsletter is making a call to the database. Scot’s Newsletter has never worked this way in the past. So it’s a learning experience.
Read the rest of this entry »

My Bonehead Move

Saturday, December 15th, 2007

Quick note to let regular blog readers know that the blog was down for most of Friday Eastern Standard Time due to “user error.” I made a configuration tweak to the database that required a corresponding tweak to the WordPress software — only I stupidly didn’t check the blog site so I didn’t know something more was needed. Once I realized (thanks to Mike Nash for alerting me), it was a 5-minute fix, nothing to worry about.

So, to summarize … Scot stupid, Mike Nash good Samaritan, blog site just fine.

Blog-Site Performance Issues

Friday, December 7th, 2007

Yesterday’s blog-entries-announcement newsletter, which went out late morning EST to both HTML and Text edition subscribers, taught me something important: My current web server arrangement is not going to stand up to the first hour after the newsletter is mailed each month.

Many of you wrote to me to tell me you either got error messages or had to wait minutes for individual blog stories to load in your browsers. Some of you just assumed that this was the normal experience at Scot’s Blog, and that is just not the case. Most of the time it’s pretty snappy.

The problem boils down to this: WordPress (and all other blog packages I’ve inspected) use a database to store the stories in. Many of them, including WordPress, use MySQL. My forums also uses a separate MySQL database. The two databases are on the same server. And the arrival of the blog newsletter quickly maxed out the number of simultaneous connections that my webhost has limited my MySQL service to. So people either got “database connection” errors or just waited and waited for the server’s time to free up. The forums also experienced interruptions and slow page loads.

Read the rest of this entry »

Windows XP or Vista?

Saturday, December 1st, 2007

There are two main types of Windows users in the world. Which kind are you:

Windows XP or Windows Vista?

The recent news that testers at Devil Mountain Software found Microsoft’s beta of Windows XP Service Pack 3 to be 10% faster than XP SP2 has pushed me over the edge.

I honestly find no advantage to Windows Vista, and there are some downsides. For example, no matter what Vista advocates say, Vista requires Vista-level hardware. Pentium M/Centrino single-core notebook hardware just doesn’t run it well. Pentium 4 desktop hardware runs it better, but usually that class of hardware needs a video upgrade. I’ve personally seen instabilities with the shipping version of the Vista code: applications freezing, Windows services slowing to a crawl, even OS crashes. I’m not saying everyone is having these problems, but I see no real improvement over Windows XP. While the architecture of Vista is a little better, Vista adds a lot of overhead to support quite a bit of new and sometimes questionable functionality. Vista is a lot more complex than Windows XP. It’s probably more secure, but it still needs a raft of third-party security software and hardware. I don’t trust its anti-malware protection or its firewall. And it doesn’t have an onboard antivirus product.

Read the rest of this entry »

The State of Scot’s Newsletter

Saturday, December 1st, 2007

I’m really tired of the Rolling Stones.

There, I got that off my chest. But it’s not what I wanted to tell you.

Now, about the blog, newsletter, whatever it is — Scot’s Newsletter. Here’s where things stand.

There’s a lot to do on the blog and newsletter sites to stitch them together, make them work in tandem. I want to combine them, not replace the old with the new. I’m feeling my way toward that, gradually. But at some point, major surgery will probably occur. For now, my recent promotion and ongoing physical therapy take priority. But I am planning in my minimal spare time.

Performing surgery on the WordPress code — except where related to design — is proving to be more difficult than I’d hoped. And the mods available for WordPress aren’t all that great. I’ve received lots of excellent suggestions from the newsletter’s readers for making the blog work better. People generally would prefer that the blog entries weren’t separate permalink pages. Many would also like the same kind of navigation the HTML newsletter offered, with a TOC at the top linking down to each item and a “back to top” link at the end of each entry. I’d prefer that too, but it’s not as easy to refit the blog code as you’d think.

Another recurring theme I hear from readers is the desire to make it easy to print “an issue.” The concept of separate monthly issues is blurring, to be honest. Much quicker than I’d expected, I find myself writing individual blog posts on different days. It seems to me that the content is better when I write it this way. But it’s a judgment call as to what items are in a specific issue. The blog software archives by calendar month.

So, anyway, the problem with printing isn’t the printing itself, but the fact that you’re not printing an issue, per se. Also, you need to print the stories pretty soon after you get the text-based blurb-and-link newsletter because as I add new posts, ones from the bottom roll off the main page into the archive.

What I’m currently doing is leaving all the latest entries at their full length, and the ones from the “last issue” will be abbreviated with a “read more” link. I’m also setting the “Recent Posts” column to show only the stories in the current “issue.” I don’t know where this will lead, to be honest. This could be transitional, or it might be my solution. I still have a lot of thinking to do to make the user experience the way I want it.

One thing I want to make very clear: This Is Much Easier for Me! I appreciate the support of so many of you who agreed to something very different even though you might not really have wanted that change. Everything about this is better, easier, faster, and less expensive. It also lets me focus researching and writing content instead of the tedium of production hassles.

The New Newsletter

Those of you getting the notification newsletter are seeing the first rendition of a new template this week. Drop me a note if you have a suggestion. It’s a work in progress.

All newsletter subscribers should be advised that my newsletter distributor, Dundee.net, will shortly be merging the HTML and Text lists into a single list for the notification newsletter. That change saves me money and time, but the main reason to do it is that it will greatly simplify the subscription tools. Subscribing, unsubscribing, and changing your email address all become much more straightforward processes. You’ll still need to receive a confirmation email and click the confirmation link it contains to verify intent to subscribe (also on email-address changes), but most of the problems that people have with the Scot’s Newsletter subscription tools will vaporize when there’s only one list.

What does merging the two lists mean for you? For most people, nothing. Both the process and the result of the merging should be invisible. People who are currently subscribed to both the HTML and Text lists with the same email address should find that they’re subscribed only once. If you’re subscribed to both lists with two different email addresses, you’ll have two subscriptions to the same newsletter after the merging. You can simply unsubscribe one of them.

During the merge period, the subscription center may be down for hours or days.

Well, that’s it for now. I’ll keep you posted on changes as I schedule them.