#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 Johannes Maron):
Ok, I should have withheld any performance claims w/o proof. But since I
ran out of my monthly token rations, let's park that discussion.
---
In my humble opinion, I thought it to be reasonable to assume that
`RedisCache.aget` actually calls the async stack of the Redis SDK.
I certainly did and tripped on the fact it wasn't. I am aware that
connection management is a complication. But just because something is
hard has never stopped us before. <3
--
Ticket URL: <https://code.djangoproject.com/ticket/37156#comment:3>
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/0107019eb5efea8a-0b2cbda1-4e2d-4b42-b963-943928bb0c47-000000%40eu-central-1.amazonses.com.
