My philosophy is to not optimize until you need to. That said, if you've got 500 tables in your app, you probably don't want to use the web2py default table instantiation on every request.
Any idea what you're traffic will be like? Are you going to load balance? Our main app has over 150 tables and is load balanced so we only load the tables we need for the request and we use redis for sessions. Other than that make sure you have a well-designed database and have the indices in place where they can help with database requests. -Jim On Thursday, July 20, 2017 at 9:58:47 AM UTC-5, [email protected] wrote: > > > There are several sections in the web2py documentation that showed some > strategies to optimize the performance of web2py, i.e. using lazy table, > memcache, etc... > > Should I incorporate some of these strategies on a new deployment of > web2py, or should I just stick with the standard configuration and optimize > only when performance becomes an issue? > > Thanks! > CD > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
