If you cache db().select() results cache.ram should be allrigths as every user/session can be operate in isolation without issue... This wouldn't be the case for things that need to be up to date for all the users at the same time, global variables for instance even if they are the result of bad dessing in the first place they are sometimes required... Though you may not realize great performance improvement with cache.ram if user (the same user) don't call your select often... So depend of what the results of the select contains you may be better setup redis cache for greater performance improvement and better memory usage (as single select instance requires less memory than session cache.ram for each user).
If you consider redis cache you have to set a proper time expiration so you improve performance and keep accessed in a relative meaningful up to date state considering the criticality of these data... Richard On Tue, Apr 26, 2016 at 11:24 AM, Pierre <theognis0...@gmail.com> wrote: > Anthony, you wrote this some time ago : > > >Are you using nginx/uwsgi? If so, I believe cache.ram would not be shared > across the different uwsgi worker processes. You might consider switching > to the >Redis cache. > >Anthony > > I know nothing about the Redis cache. Wikipedia says this is NOSQL and > web2py is SQL so is this 'cache-business' science fiction ? > > -- > 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. > -- 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.
