#37156: Properly implement async Redis methods
-------------------------------------+-------------------------------------
Reporter: Johannes Maron | Owner: (none)
Type: | Status: new
Cleanup/optimization |
Component: Core (Cache system) | Version: 6.0
Severity: Normal | Resolution:
Keywords: redis, asyncio, | Triage Stage:
async | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
FWIW pending full write up: overhead of sync_to_async is in the low
microseconds range, and there's **no measurable gain** (in fact a small
loss) at the redis client level.
The ergonomics here are that RedisCache offers an async API. Whether it
"actually calls the async stack of the Redis SDK" is an implementation
detail. There's a serious question as to whether there is **any benefit**
to us maintaining parallel/duplicate code paths here.
As I say, I'll write up more, but that's how I'm leaning.
--
Ticket URL: <https://code.djangoproject.com/ticket/37156#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019eb5f655d3-ccd90a93-276c-4ce7-919a-dd2c15cccc11-000000%40eu-central-1.amazonses.com.
