Performance optimisations in the deployment checklist document

[Marc Tamlyn]

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 said, if you're not using `CONN_MAX_AGE`, then there's a huge benefit.

The only issue I can see is that it only improves performance if you've got memcached installed. That's easy to state though, and a reasonably large number of users will be using caching anyway.

Any thoughts?

Marc

[Tim Graham]

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.

[Daniele Procida]

On Fri, Aug 16, 2013, Tim Graham <timog...@gmail.com> 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
>something to consider.

There should presumably also be a similar pointer to this topic in the general optimisation and performance documentation described in <https://code.djangoproject.com/ticket/20877>.

Daniele

[Marc Tamlyn]

Opened https://code.djangoproject.com/ticket/20938

--
You received this message because you are subscribed to the Google Groups "Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
For more options, visit https://groups.google.com/groups/opt_out.