On Friday, March 8, 2019 at 4:55:02 AM UTC-5, icodk wrote: > > So if I understand it right, web2py caches compiled application files and > do it on the first demand or a source change and never write back to > storage/disk. If so, Is there any advantage for compiled web2py > application (except the one time load and compile after web server reset)? >
For model files, as you suggest, aside from the initial load, I don't think the compiled files offer an advantage. There is a small advantage for controller files, as in the non-compiled case, web2py still parses the (cached) non-compiled code to identify all the function names. The biggest advantage of compiling is with the views, as web2py does not internally cache compiled view code in memory. Anthony -- 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.
