3 ms·
> CPython was never explicitly engineered for performance, whereas the JVM had decades of work poured into it. * Often IO latency and throughput is such that f
by rdtsc 15y ago
> CPython was never explicitly engineered for performance, whereas the JVM had decades of work poured into it.
* Often IO latency and throughput is such that fast CPU processing doesn't really matter. IO is the bottleneck and Python is often fast enough.
* Look @ speed and improvements in PyPy (keeping in mind their team size and budget) in just recent years vs JVM's man hours over the years. Just because there were decades of performance poured into it, doesn't make something proportionally better.
- ezyang 15y agoInterestingly enough, I was talking to Quora engineers about the problems they were facing scaling their website, and there was no doubt about it: CPU was one of the big problems. Yes, yes, I know, don't overengineer your systems in the beginning, but I really get the sense that if software needs to scale, it is going to need to scale in all dimensions, including CPU. I'll note that the "JVM has had more hours poured into it" argument is meant to give PyPy the benefit of the doubt!
- barrkel 15y agoAdd enough concurrent connections and CPU will be a bottleneck again.