Joel Liu's Library tagged twitter →  View Popular

All of that is great, the problem is that it’s hard to teach an old dog new tricks. Delicious has long just been about saving links and not about sharing them like many of the new, more versatile social sharing services out there. If Yahoo wanted to tie the product into Twitter, it should have done that months ago, to get ahead of the curve, rather than at the back of it.

The problem now is that there are plenty of other services people are already using to share stuff on Twitter. Most people still just paste links right into the update box, and Twitter uses Bit.ly to shorten them. This is allowing Bit.ly to collect a huge amount of data about what people are sharing — something which it could use soon to take on Digg and Delicious.

• Web is only 10-20% of the traffic, the rest is through API services
• Web servers are still 50% of the cluster.
• Regular incoming traffic peaks are around 80 tweets per second. I expected this to be a lot more.
• before the upgrades their web servers shipped only 3.32 requests per second!
• For each tweet, message gets inserted for each user which follows a tweet. In average, a user has 120 followers so this comes to about 9600 messages/s at peak times
• Message servers run on three nodes. They decided to write their own messaging software in order to make the protocol memcached-like, and did not evaluate other available solutions.
• During Obama’s inauguration, they peaked at about 350 tweets per second for around five minutes.
• They had a ton of problems with garbage collection but strangelly haven’t looked into JRockit RT or something similar that has predictable GC. Twitter JVM middleware runs on the SUN JVM