4 ms·

Not entirely true that the database is the main concern[0]. The overhead of the framework/language has a massive impact. That said, I'm not Google either, and

Not entirely true that the database is the main concern[0]. The overhead of the framework/language has a massive impact. That said, I'm not Google either, and I'm happily using django and love using it. [0] http://www.techempower.com/blog/2013/03/28/frameworks-round-1/ http://www.techempower.com/blog/2013/03/28/frameworks-round-...

est 13y ago
How about in Round 7 that Python surpasses Nodejs? http://www.techempower.com/benchmarks/#section=data-r7 http://www.techempower.com/benchmarks/#section=data-r7 Python didn't beat NodeJS in Database queries though. Yes Go is fast, but Go is also cluttered with its static type system. Personally I feel pain to deal with flexible JSON marshal/unmarshal, in Python dict() is nearly 100% identical with JS objects in value.
- jsmeaton 13y ago
  > How about in Round 7 that Python surpasses Nodejs I can't find what you're referring to. Node was still infront of Django in the JSON benchmark. Django (until 1.6) hasn't had connection pooling for the database either. Updating those benchmarks with pooling should make significant differences. But my point was that the framework itself can have a huge impact. Database and other I/O does have overhead, and it may even be significant. But it's not necessarily the biggest factor.
  - est 13y ago
    You are comparing a Web framework (Django) with a language+network runtime (Nodejs). The Nodejs web framework is Express, behind Bottle and Falcon.
    - jsmeaton 13y ago
      Oh, I see. But "python" wasn't represented, which confused me. There is still a large discrepancy between the different frameworks in the javascript and python set. But the original point was that database and I/O make the largest difference. After restricting the set of languages and frameworks to python and javascript, I can only (now) agree. 109,000-5700 rps for JSON requests, and 4800-117 rps for multiple database queries. Quite significant.
      - est 13y ago
        I agree with ya. There's big room for db connection improvement in Django.

est 13y ago

How about in Round 7 that Python surpasses Nodejs? http://www.techempower.com/benchmarks/#section=data-r7 http://www.techempower.com/benchmarks/#section=data-r7 Python didn't beat NodeJS in Database queries though. Yes Go is fast, but Go is also cluttered with its static type system. Personally I feel pain to deal with flexible JSON marshal/unmarshal, in Python dict() is nearly 100% identical with JS objects in value.

jsmeaton 13y ago
> How about in Round 7 that Python surpasses Nodejs I can't find what you're referring to. Node was still infront of Django in the JSON benchmark. Django (until 1.6) hasn't had connection pooling for the database either. Updating those benchmarks with pooling should make significant differences. But my point was that the framework itself can have a huge impact. Database and other I/O does have overhead, and it may even be significant. But it's not necessarily the biggest factor.
- est 13y ago
  You are comparing a Web framework (Django) with a language+network runtime (Nodejs). The Nodejs web framework is Express, behind Bottle and Falcon.
  - jsmeaton 13y ago
    Oh, I see. But "python" wasn't represented, which confused me. There is still a large discrepancy between the different frameworks in the javascript and python set. But the original point was that database and I/O make the largest difference. After restricting the set of languages and frameworks to python and javascript, I can only (now) agree. 109,000-5700 rps for JSON requests, and 4800-117 rps for multiple database queries. Quite significant.
    - est 13y ago
      I agree with ya. There's big room for db connection improvement in Django.