News for hackers. Stuff that matters.
Re:PyPy and Psyco by moe on Sunday March 15, 2009 @04:15PM (#517196)
Maybe because raw excution speed matters so little in most applications that they're rather focussing on lower hanging fruits such as improvements to the core language or standard library. - But that's just a wild guess.
Re:PyPy and Psyco by ankhmoop on Monday March 16, 2009 @01:57AM (#517827)
Raw execution speed does matter, but like any incremental cost, is often ignored.

Off-the-cuff benchmarks I ran on our Scala-based webapp on a four-core desktop system demonstrated 5,000 req/sec @ 2ms/request after the JIT warmed up.

5,000+ requests/second -- scaling up with available CPUs -- means not having to worry about performance, complicated caching, and the slew of other things that developers do to eek performance out of frameworks based on poor interpreter implementations.

Re:PyPy and Psyco by moe on Tuesday March 17, 2009 @08:10AM (#519755)
It's not really an incremental cost but rather a constant overhead.

The idea is that if you're worried about performance and scaling then you'll have to find a way to distribute your load over multiple physical machines anyways.

At that point it doesn't matter so much anymore whether one of your nodes handles 5000 reqs/sec or 2500 reqs/sec. Hardware is cheap.

Re:PyPy and Psyco by ankhmoop on Tuesday March 17, 2009 @02:53PM (#520368)
"Hardware is cheap" is a false dichotomy. The implication is that hardware is cheap, but development is not, and performant architectures require expensive development.

In reality, neither hardware or development are cheap, and performance does not inherently necessitate more costly development. The mantra and the dichotomy are false.

Re:PyPy and Psyco by mojonixon on Sunday March 15, 2009 @05:16PM (#517258)
Raw execution speed matters when dealing with Google sized data sets, but Google and organizations with similar requirements can just throw more hardware at it.
Re:PyPy and Psyco by anamax on Sunday March 15, 2009 @09:45PM (#517587)
Google uses C++ for compute-bound stuff.

Google's problems are big enough that constants matter.