4 ms·
A stripped down version of Django - no unnecessary apps installed. This was recommended to test Django's full speed but really wouldn't be reflective of a full
by cmsimike 13y ago
A stripped down version of Django - no unnecessary apps installed. This was recommended to test Django's full speed but really wouldn't be reflective of a full deployment.
- mixmastamyk 13y agoIt's disappointing that it's so slow. I suppose it doesn't matter a lot of the time, but would prefer it to be more competitive.
- amarsahinovic 13y agoIn the previous benchmark it was pointed out that they don't use connection pooling [1], I don't know is it fixed in this round https://news.ycombinator.com/item?id=5499490 https://news.ycombinator.com/item?id=5499490
- andybak 13y agoThey don't say either way but it requires them to switch to Postgres so I think they would have said if they had.
- bhauer 13y agoThat's correct; we are still testing on MySQL, so the Django tests are still configured without a connection pool. We would love a pull request that incorporates a connection pool for Django+MySQL. We do have Postgres as a target for future rounds of this project, but do not yet have an ETA for that.
- andybak 13y agoI wonder if this would be sufficient: https://pypi.python.org/pypi/django-mysqlpool/0.1-7 https://pypi.python.org/pypi/django-mysqlpool/0.1-7
- zalew 13y agooh, I see https://github.com/TechEmpower/FrameworkBenchmarks/blob/master/django-stripped/hello/hello/settings.py#L92 https://github.com/TechEmpower/FrameworkBenchmarks/blob/mast... I guess it was about sessions and auth hitting the db?