News for hackers. Stuff that matters.
Re:Web Service Efficiency at Instagram with Python by wheaties on Tuesday June 21, 2016 @05:52PM (#11949714)
Wow, CPU is the limiting factor? I've never been CPU bound in a Web app, only I/O bound. Am I doing something wrong?

Granted, I don't use python anymore for Web dev. I'm using languages that can handle 10x the traffic per box that Django used to be able to handle. This isn't a knick against python. I love python. Just such a different perspective.

Re:Web Service Efficiency at Instagram with Python by hardwaresofton on Tuesday June 21, 2016 @06:42PM (#11950043)
This also immediately popped out to me as the wrong assumption to make (and start off with, for that matter)... But I could see it being true if:

- You are essentially maxing out incoming and outgoing network IO

- You have no database to speak to (or your DB is in-memory)

In that case, I guess it is just a race to do some computation and fetch the right data from RAM, then the limiting factors would be RAM access and the number of the computations you could do to try and keep up with inbound requests?

Re:Web Service Efficiency at Instagram with Python by pbreit on Wednesday June 22, 2016 @01:08AM (#11951689)
I'm guessing that you're working on something that is fractionally as successful as Instagram. Getting to the point where you need to scale is hard, scaling is easy.
Re:Web Service Efficiency at Instagram with Python by dchuk on Tuesday June 21, 2016 @09:16PM (#11950918)
What languages/frameworks are you using now?