The answer is - yes maybe, but there is no such thing as "django
site". Most of the time the bottlenecks are somewhere else (as you can
see, the admin does not help you) and is often something stupid (e.g.
like here people defining classes at runtime for no good reason) that
has to be looked on a c
Wow, that's what I call customer support! :) Can confirm PyPy is better
than CPython on the admin now, post warmup.
You're right, it doesn't help my site very much, but that's my fault for
preparing the wrong benchmark fixture. :)
On the other hand, it doesn't really make sense for you PyPy d
It got merged into django, PyPy (2, didn't test the 3) is now faster
than cpython on django admin. It likely does not help your cause
though so you need to come up with a better benchmark :-)
On Sun, Feb 8, 2015 at 8:30 PM, Maciej Fijalkowski wrote:
> Hey Tin.
>
> We are in the process of two (tr
Hey Tin.
We are in the process of two (trivial) pull requests to django that
drop the rendering time from 25ms -> 8ms for this case. I'm not a
farseer, however I suspect something like this can be done with your
site too (depending what it really does).
On Sun, Feb 8, 2015 at 8:23 PM, Tin Tvrtkov
Hello,
thanks to everyone for their input (especially Maciej).
Since I've ripped out all my code from the test project, it's not a
Python 3 project anymore, so I did try PyPy 2 with it too. It's faster,
yes; the last test looked something like:
PyPy 2 20.206 [ms] (mean)
PyPy 3
then it's used in the wrong ways in say django admin, look at
invocations to lazy there (this is how it showed up in my profile)
On Sun, Feb 8, 2015 at 5:08 PM, Alex Gaynor wrote:
> FWIW, I've definitely seen and worked on Django sites that got major
> improvements out of PyPy -- both the templat
FWIW, I've definitely seen and worked on Django sites that got major
improvements out of PyPy -- both the templates and ORM are both sped up
substantially by it. I think we should try to fix issues as we see them,
before writing it off.
FWIW: lazy does not create a new class per call of a function
I don't know :-( not sure if fixing those issues one by one is the way
to go, it's not like *this* particular code is a problem, it's the
culture that breeds those sort of things
On Sun, Feb 8, 2015 at 2:09 PM, Omer Katz wrote:
> Isn't there anything we can do about it?
> We can open issues at th
Isn't there anything we can do about it?
We can open issues at the Django issue tracker if some code slows down
execution in PyPy.
2015-02-08 12:17 GMT+02:00 Maciej Fijalkowski :
> Hi Tin
>
> I have a bit sad news for you, but essentially from what I looked at
> profling, the answer seems to be "
Hi Tin
I have a bit sad news for you, but essentially from what I looked at
profling, the answer seems to be "don't use django, it has not been
written with performance in mind". For example here (which features in
django admin quite prominently, some stuff calls lazy() at each call):
https://gith
10 matches
Mail list logo
