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 -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
