Twitter.com gets a performance upgrade

As Twitter has become more and more popular, there have been times when its users see the "fail whale" graphic on the Twitter.com site. That almost always means that the site is suffering from a high amount of traffic. This week, Twitter's blog page announced plans to boost the performance of the Twitter.com site.

The problems actually started in 2010, when Twitter decided to move much of the rendering of the site to its user's browsers. Now Twitter admits that move " ... lacked support for various optimizations available only on the server."

So Twitter has decided to move the rendering back to its servers. The company said, "This has allowed us to drop our initial page load times to 1/5th of what they were previously and reduce differences in performance across browsers."

The highly technical blog entry also discusses other plans to speed up performance on the site, including eliminating the hashbang (#!) in Twitter.com URLs. Twitter states, "By removing the need to handle routing on the client, we remove many of these steps and reduce the time it takes for you to find out what’s happening on twitter.com."

The company is putting these improvements in place but at the moment there's no word on when it will be fully implemented.

Source: Twitter blog

Report a problem with article
Previous Story

Crysis 2 returns to Steam's library

Next Story

TechSpot: Android 4.0: Tracking ICS' Availability on Smartphones

16 Comments

Commenting is disabled on this article.

I've been complaining about this for a while now, Twitter has been one of the SLOWEST sites on the net right now, more times than not, not working. Glad they're fixing it.

I'm so used to using apps I completely forgot how slow the twitter.com site was. Good to see they're finally trying to improve it.

Will this also fix the issue with tweets not showing up on the timeline eg sticking. It's slightly better now but I'm still missing some people's tweets.

Meph said,
Yessss! No more hashbangs. Another win for accessibility!

I wonder if they will replace it with the History API. github is a nice example how well this works in not too oldish browsers.

theyarecomingforyou said,
I've got another way they can speed up page loads - reduce the character limit to 20. That would also remove most of the inane drivel that people post. Win!

Oh yeah, that way we can get tweets with only a link.. spambots will love that!

theyarecomingforyou said,
I've got another way they can speed up page loads - reduce the character limit to 20. That would also remove most of the inane drivel that people post. Win!

Another way is to make use of the unfollow button.

theyarecomingforyou said,
Or simply not use the service.

That's a bit overkill. If you don't like the stuff someone tweets, just stop following them and you'll never have to see it again. Pretty simple concept really.

theyarecomingforyou said,
Or simply not use the service.

Exactly, so shut up, don't use the service and leave it to others to enjoy.

20 characters... yeah cuz that would work, wouldn't it?

You know what's even better?? When navigating to permalinks, you no longer have to wait for the homepage to load, then for it to go blank, then for it to load the tweet that you've directly linked to (this was caused by the hashbang, and so still happens on the 'Connect' pages).

That's been driving me insane for ages.