Opened https://code.djangoproject.com/ticket/20938
On 16 August 2013 20:01, Daniele Procida wrote:
> On Fri, Aug 16, 2013, Tim Graham wrote:
>
> >I don't think there's a reason to recommend one of the two cached sessions
> >backends over the other as the choice is application dependent, but +1
On Fri, Aug 16, 2013, Tim Graham wrote:
>I don't think there's a reason to recommend one of the two cached sessions
>backends over the other as the choice is application dependent, but +1 on a
>link to
>https://docs.djangoproject.com/en/dev/topics/http/sessions/#using-cached-
>sessions as
>so
I don't think there's a reason to recommend one of the two cached sessions
backends over the other as the choice is application dependent, but +1 on a
link to
https://docs.djangoproject.com/en/dev/topics/http/sessions/#using-cached-sessions
as
something to consider.
On Thursday, August 15, 20
I think we should at consider mentioning the `cached_db` session engine in
the performance considerations part of the deployment checklist. It's an
easy setting to enable which does give a performance boost, although the
hit caused by it is decreased now we have persistent connections. That
sai
