#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
-------------------------------------+-------------------------------------
Description changed by Johannes Maron:

Old description:

> The backend API already implements `aget`, `aset`, … methods.
> However, the native `RedisCache` backend, doesn't reimplement those
> methods to use the asyncio API of the Redis SDK, but rather the asgiref
> fallback.
>
> As discussed before, the extra threading comes with a significant
> overhead and disrupts things like full-page caching of otherwise async
> views.
>
> This proposal does not alter Django's public API, but rather optimizes
> internal implementation, which is why I put this on Trac.

New description:

 The backend API already implements `aget`, `aset`, … methods.
 However, the native `RedisCache` backend, doesn't reimplement those
 methods to use the asyncio API of the Redis SDK, but rather the asgiref
 fallback.

 ~~As discussed before, the extra threading comes with a significant
 overhead and disrupts things like full-page caching of otherwise async
 views.~~

 This proposal does not alter Django's public API, but rather optimizes
 internal implementation, which is why I put this on Trac.

--
-- 
Ticket URL: <https://code.djangoproject.com/ticket/37156#comment:4>
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/0107019eb5f10bce-f727ec83-dfa5-4049-966e-0b39c578e863-000000%40eu-central-1.amazonses.com.

Reply via email to