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.
