News for hackers. Stuff that matters.
Re:Why interpreters matter (at least for high level programm... by btilly on Sunday May 13, 2012 @03:07AM (#3966268)
The memory point is huge.

For your decently coded basic webserving app, the bottleneck is almost never your code. It is the network, databases, etc. And in my experience, the bound on how many simultaneous requests you can serve is generally not your CPU. It is how much memory it takes to have enough processes ready to handle requests. (Admittedly my experience is mostly with Perl, where multi-threaded code is a bad idea. But Python has the GIL, so again I would plan on using more processes instead of heavily multi-threaded code for concurrency.)

Given this, for the kinds of web applications that I have worked on, reducing memory consumption is the thing that most helps scalability.

There are no comments on this comment yet.