On Wednesday, April 27, 2016 at 7:00:53 AM UTC-4, Pierre wrote: > > I'm impressed Anthony... > > well all of these - memcache-redis - seem to require lot's of technicality > and probably to set-up your own deployment machine. I am not very > enthusiastic about that option since the internet if full of endless > technical setup-config issues. Given what's being said, I see only two > kinds of page of my app I could cache : general informations and maybe > forms (no db().select()) all shared and uniform datas. >
I'm not sure what you mean by caching forms, but you probably don't want to do that (at least if we're talking about web2py forms, which each include a unique hidden _formkey field to protect against CSRF attacks). > There should be a simple way to achieve such a simple thing whatever the > platform: pythonanywhere,vs......Is there one ? > You can just use cache.ram. If running uWSGI with multiple processes, you will have a separate cache for each, but that won't necessarily be a problem (just not as efficient as it could be). You could also try cache.disk and do some testing to see how it impacts performance. More generally, caching is something you do to improve efficiency, which becomes important as you start to have lots of traffic. But if you've got enough traffic where efficiency becomes so important, you should probably be willing (and hopefully able) to put in some extra effort to set up something like Memcached or Redis. Until you hit that point, don't worry about it. 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
