every request maps to your application/controller/function - for each request, all models are read prior to the selected controller call.
Theoretically, reducing the number of files read in should speed things up - BUT the reality of the speedup is probably not what you might expect; models to not do any more than setup the python data structure for interacting with results of queries, and you would expect that - except for perhaps the first request to an app in a long time, that host disk caching would minimize effect of opening "lots" of small files. Still, there should be some effect, and 93 tables is A LOT. If 4-6 at a time are all that are needed, another possibility is to look at the structure for each call and consider refactoring into functionally / logically related calls, and break this into several cooperating web2py apps. On Tue, Sep 29, 2009 at 9:55 AM, Jonathan Lundell <jlund...@pobox.com>wrote: > > On Sep 29, 2009, at 7:03 AM, mdipierro wrote: > > > If you still need more speed move the table definitions in a module > > (not a model) and import it from the model. I would not recommend this > > to everybody but 93 is a lot. > > How does that speed things up? (Just curious.) > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
