On Friday, April 20, 2018 at 11:58:47 AM UTC-4, Lisandro wrote: > > I see what you mean. > But still, if my interpretation is correct, in those cases we should see > the *__lock key stored. > What is weird about my specific issue is that there was no *__lock key. > > Anyway, regardless upgrading web2py, now I'm wondering if I should set > with_lock True or False. Do you have any suggestion? The book says: > "*Redis cache subsystem allows you to prevent the infamous "thundering > herd problem": this is not active by default because usually you choose > redis for speed, but at a negligible cost you can make sure that only one > thread/process can set a value concurrently.*" > > I haven't found comments regarding when is best to use with_lock=True and > when to use with_lock=False. >
Probably safest to set it to True unless that slows things down noticeably. Or go with False if you can tolerate the occasional race condition. 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.
