Just think about it loading a page that queries from one table, and models that define 200 tables. For that single query 200 tables must be define with the default web2py setup. This isn't rocket science to know it will be wasting a lot of resources and slow down performance every extra function call will cause performance problems on a high traffic website. Lets not forget with every model definition it will use more memory.
Another performance problem is translations for sites with a lot of translations strings as the entire dictionary must be loaded into memory. This part I am still thinking whether having a different file per action would be worth it to improve speed. On Tue, Jul 17, 2012 at 9:40 AM, Bruce Wade <[email protected]> wrote: > LOL well the before and after performance improvements from moving the > models has proven it to be a major problem. So yes models are definitely a > problem primarily because they are redefined every call and with a high > traffic site that means a lot of redefinitions. > > On Tue, Jul 17, 2012 at 9:12 AM, pbreit <[email protected]> wrote: > >> I'd be surprised if model processing is your biggest problem. Have you >> reviewed all your queries for optimization opportunities? Cache, cache and >> more cache? Indexes? >> >> -- >> >> >> >> > > > -- > -- > Regards, > Bruce Wade > http://ca.linkedin.com/in/brucelwade > http://www.wadecybertech.com > http://www.fittraineronline.com - Fitness Personal Trainers Online > http://www.warplydesigned.com > > -- -- Regards, Bruce Wade http://ca.linkedin.com/in/brucelwade http://www.wadecybertech.com http://www.fittraineronline.com - Fitness Personal Trainers Online http://www.warplydesigned.com --
