Re:7 Years Of YouTube Scalability Lessons In 30 Minutes
by cbsmith on Monday March 26, 2012 @02:33PM
(#3758006)
I honestly don't understand why they simply don't use out of sync data. You could have nodes periodically send aggregates of likes & views, and then add those in to the total ever N heartbeats. Why bother fudging the in-between.
Re:7 Years Of YouTube Scalability Lessons In 30 Minutes
by moe on Monday March 26, 2012 @08:25PM
(#3759329)
They're probably propagating the likes and views independently. Which still doesn't explain why they allow counter-intuitive gaps like that instead of fixing them up on the client-side in javascript.
Re:7 Years Of YouTube Scalability Lessons In 30 Minutes
by modeless on Monday March 26, 2012 @10:25PM
(#3759680)
Yeah, the view counter is a clear case where they've gone too far. People care about view counts and it seems like every other video I watch has people complaining in the comments about the view count being obviously wrong.
Re:7 Years Of YouTube Scalability Lessons In 30 Minutes
by batiudrami on Monday March 26, 2012 @11:51PM
(#3759925)
The only time I notice this is when the view counts freeze at 300-ish for a few hours. That's because they're checking if the views are legit or from a bot, IIRC.
I knew the view counter wasn't propagated but the likes were and I was like: "Damn this is Youtube, kinda disappointing..."
I guess if both were propagated at the same time I wouldn't mind.