So for everybody.... let me summarize this: Thanks to Alexey, the web2py in trunk can execute models 2.5x faster than the current stable/production version (requires migrate=False and bytecode compiled models). This is a general result since each define_table speeds up the same. For his particular app, this results on a speedup of 70% when serving pages (this number depends on the app).
There is also the possibility of an additional 70% speedup of the models by implementing additional tricks. We'll keep working on this. Massimo On Jun 8, 10:41 am, Alexey Nezhdanov <[email protected]> wrote: > On Monday 08 June 2009 19:27:29 Alexey Nezhdanov wrote: > > > On Monday 08 June 2009 19:18:26 mdipierro wrote: > > > I understand what you say below but I think it is important to measure > > > the total speedup from the original/stable sql.py and the one in trunk > > > on the same machine and same complex model that you have. > > > NP, it is running right now. Quite slow, will finish in ~10minutes. > > Revision 875: > model 0.04167 > min 0.05579 > avg 0.0559455 > max 0.05647 > > Revision 882: > model 0.01646 > min 0.02979 > avg 0.03267 > max 0.03597 > > 882+optimised inits: > model 0.01380 > min 0.02697 > avg 0.03003 > max 0.03189 > > 882+optimised inits + lazy tables: > model 0.01009 > min 0.02555 > avg 0.0297105 > max 0.033360 > > model 0.01012 > min 0.02369 > avg 0.02983 > max 0.03340 > > model 0.00966 > min 0.02415 > avg 0.02850 > max 0.03208 > > -- > Sincerely yours > Alexey Nezhdanov --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
