New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using dbm locking one can not create values with nested creators #5
Comments
Michael Bayer (zzzeek) wrote: is that the file lock freezing ? OK we can make it re-entrant, perhaps beaker's did this already |
Michael Bayer (zzzeek) wrote: oh, that's the dogpile. OK might want to put a reentrant decorator around the lock in a generic way....hooray latency |
Michael Bayer (zzzeek) wrote: still thinking sorry ! the dbm backend's lock is across all keys. other locks dont. so maybe a reentrant proxy chosen by the backend depending on the type of lock. |
Changes by kaukas (kaukas):
|
Michael Bayer (zzzeek) wrote: okey doke got something for this in [[https://bitbucket.org/zzzeek/dogpile.cache/changeset/c2e2571f326f5a990a52c75f4739800012c82493|c2e2571f326f5a990a52c75f4739800012c82493]]. Should be good to release 0.2.3. |
Changes by Michael Bayer (zzzeek):
|
Migrated issue, originally created by kaukas (kaukas)
Sometimes it is desired to cache not only the final result of the computation but the intermediate steps as well. Doing that you can invalidate the result of some of the steps and the final cache. The recomputation of the final result would then be faster because it would still use the rest of the cached values.
Example:
The above code freezes - once the lock is acquired for the "big thing" you can not store "small things".
The text was updated successfully, but these errors were encountered: