Thanks for confirming this issue. The other thing I noticed is that if I just go ahead and create an instance of CacheInRam and CacheOnDisk, and combine them as before, and go ahead and use them - this would mean that a cache ram & disk instance is created for practically every request, wasteful - but then I do not see this locking happening. So, this locking is an issue with the same instance being used to access the disk cache ... and doesn't arise if different cache disk instances are trying to work recursively?
Also, if there is any help I can extend to help with this issue, please let me know. Am in the middle of putting up my building and deploying my application ... but will set aside time to help with this issue. On Thursday, October 15, 2015 at 7:59:23 PM UTC+5:30, Leonel Câmara wrote: > > Yep, the cache locks the key it's writing so this is not possible. If the > keys are not the same it still gets locked because of statistics gathering. > The only way to prevent this would be to have a disable statistics option > in cache disk, which I am inclined to develop as it would also allow truly > concurrent access to cache disk. > -- 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.
