I don't know what is memory usage... but per 'Isolated Benchmark' section some web frameworks (see those marked with asterisk) experience memory issues... aka memory leaks... It is interesting to see web2py failed pypy test, the only one. The benchmark selected for template engine is known as big table test, not very real world scenario... but still... not sure it that much important... still grab your CPU anyway. Pypy is not a problem solver,... but can do some magic to those who care... never used it in production yet.
On Thursday, October 4, 2012 1:55:11 PM UTC+3, אברהם סרור wrote: > > impressive gain when using pypy, still django seems to have the slowest > template engine > it would be interesting to see memory usage also, not only speed > btw does anyone uses pypy in production yet? care to share some thoughts? > > > On Thu, Oct 4, 2012 at 10:02 AM, Moonlight <moonligh...@yahoo.com<javascript:> > > wrote: > >> It is interesting to see how django performance is improved by Pypy 1.9 >> (vs CPython 2.7) in web >> framework<http://mindref.blogspot.com/2012/09/python-fastest-web-framework.html> >> and template >> engine<http://mindref.blogspot.com/2012/07/python-fastest-template.html> >> benchmarks. >> >> > -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/MNozzKQwXBYJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.