It is true but not an issue. Django is faster only in hello world examples because does not perform as many header validation/conversions as web2py does and because you cannot turn off sessions in web2py. As soon as one uses templates, web2py is faster. If you use databases the speed is about the same because that becomes the bottle neck.
Massimo On Monday, 8 July 2013 17:08:53 UTC-5, Arnon Marcus wrote: > > BTW, is it really true that web2py is twice as slower than django nowadays? > How can that be? > Didn't it used to be twice as fast? > When I first evaluated it 3 years ago, it was by-far the fastest - what > changed? > You said that one of the core principles of accepting changes to web2py, > is that they should always make it run faster - never slower. Has that > principle been broken? > And what about the whole ORM-vs-DAL fiasco? Didn't you guys always say > that a DAL is always faster than an ORM? Given that it makes sense, how > come Django is faster? Shouldn't it's ORM make it slower? > And as for executing-vs-importing - didn't you say before that it should > be a non-issue in terms of performance? What changed? > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
