Live data from Hacker News

Scaling Reddit from 1 Million to 1 Billion – Pitfalls and Lessons [video]

infoq.com

71–80 of 114 posts

Re: Scaling Reddit from 1 Million to 1 Billion – Pitfalls and Lessons [video]

#71
post #14
post #11

Reddit's not profitable though..

If there is one lesson that HN needs to learn, it's that profitable is not the same thing as important.

I think that the endless stream of stories about websites shutting down and deleting all user content has made it clear to HN users that clearing a profit is pretty important.

Re: Scaling Reddit from 1 Million to 1 Billion – Pitfalls and Lessons [video]

#73
post #48
post #7

I am curious how much a Go lang rewrite would make a difference in scaling up.

It depends how much time is spent doing computation and how much time is spent doing lookups from disk. If the latter is clearly dominating, then a switch to Go will not help much.

thanks for the insight. i did not have much to do with Go. But hear a lot of positive benchmarks here on HN. Reddit is kind of like an example social web app, and I read a lot on its architectural changes and scaling efforts. So for social Web 2.0 apps, which are getting older now, I m curious how much Go would make a difference. Mainly for Google applications, apparently Go brings a lot of speed and performance on the same server.

Re: Scaling Reddit from 1 Million to 1 Billion – Pitfalls and Lessons [video]

#74
post #14

Earlier quoted context omitted.

If there is one lesson that HN needs to learn, it's that profitable is not the same thing as important.

So they are important, but need to live off ramen every day (figuratively). What good does that do to them? I don't think grandparent should be downvoted, he raises a good point. Tons and tons of people use Reddit, but Reddit has a hard time making a living.

Power and fame are strong motivators too.

Re: Scaling Reddit from 1 Million to 1 Billion – Pitfalls and Lessons [video]

#75
post #36

Earlier quoted context omitted.

Why? Looks like a legitimate question to me.

Some time ago the HN hivemind went through a period of blind Node.js love. Now it's going through blind Go love. Regardless of what you think of either language, "rewrite in X" is not a magic incantation that will spontaneously solve all your architectural issues. Designing a good architecture involves balancing many components, of which your primary implementation language is an important, but not exclusive, element…

[deleted]

Re: Scaling Reddit from 1 Million to 1 Billion – Pitfalls and Lessons [video]

#76

Disappointment in the HN community has reached a new high today. So, instead of discussing the topics in the video, the majority of commenters here are discussing the flaws of the website it's hosted on or debating whether or not reddit is profitable. Neither of which has ANYTHING to do with scaling. I expected better, people. Seriously.

The dominance of non-relevance is interesting for HN. Was writing exact the same thing, and just saw yours.

In this and some other technical topics, people end up discussing their personal tastes with web site's design, their individual UI frustrations with some button on the web site, the font, the color, and other random non-relevant topic; like now the profitability.

Re: Scaling Reddit from 1 Million to 1 Billion – Pitfalls and Lessons [video]

#77
I was confused about the memcached problem after moving to the cloud. I understand why network latency may have gone from submillisecond to milliseconds, but how could you improve latency by batching requests? Shouldn't that improve efficiency, not latency, at the possible expense of latency (since some requests will wait on the client as they get batched)? And while maybe efficiency is valuable, why would that be an improvement for a problem they didn't have before?

Re: Scaling Reddit from 1 Million to 1 Billion – Pitfalls and Lessons [video]

#78

Disappointment in the HN community has reached a new high today. So, instead of discussing the topics in the video, the majority of commenters here are discussing the flaws of the website it's hosted on or debating whether or not reddit is profitable. Neither of which has ANYTHING to do with scaling. I expected better, people. Seriously.

Maybe they can't see the video to begin with because of excessive web advertising ploys. That might explain why they are not commenting on the video. Just a guess.

Re: Scaling Reddit from 1 Million to 1 Billion – Pitfalls and Lessons [video]

#79
post #64

Earlier quoted context omitted.

AllAdvantage was great for free money as a teenager. It only took a few minutes to slap together a VB application to move the mouse a few pixels every minute. I made a few hundred dollars from them while I slept.

I guess I didn't have my act together enough as a teenager to commit fraud over the Internet while I slept.

It wasn't really fraud. The terms of use etc weren't really clear enough or lets face it enforceable.

Was it fraud if you got a dog to play with the mouse, and never looked at the screen? The dog might have still been looking at the adverts!

Re: Scaling Reddit from 1 Million to 1 Billion – Pitfalls and Lessons [video]

#80
post #77

I was confused about the memcached problem after moving to the cloud. I understand why network latency may have gone from submillisecond to milliseconds, but how could you improve latency by batching requests? Shouldn't that improve efficiency, not latency, at the possible expense of latency (since some requests will wait on the client as they get batched)? And while maybe efficiency is valuable, why would that be an…

Sorry that wasn't clear. The latency didn't get better, but what happened is that instead of having to make a lot of calls to memcache it was just one (well, just a few), so while that one took longer, the total time was much less.
Post reply on HN