Re: Performance optimisation documents, ticket 20877

+1 to what Tim said. Most Django sites performance problems are not at the level of the python code running, rather inefficient databases/caching/templates etc. If your core logic is comparatively slow you're already past a basic optimisation guide. Keep it simple, and BENCHMARK. On 13 Sep 2013

Re: Performance optimisation documents, ticket 20877

I feel like we open a can of worms if we go down this road. Where do we draw the line between what we do and don't mention regarding *Python* optimization? The Django docs don't need to layout the current state of the Python ecosystem IMO. I don't doubt the info is helpful, but I don't think

Re: Performance optimisation documents, ticket 20877

On Fri, Sep 13, 2013, Florian Apolloner wrote: >On Friday, September 13, 2013 4:18:05 PM UTC+2, Daniele Procida wrote: >> >> Any further comments would be welcomed. There's some disagreement about >> the appropriateness of the last section, < >>

Re: Performance optimisation documents, ticket 20877

Hi Daniele, On Friday, September 13, 2013 4:18:05 PM UTC+2, Daniele Procida wrote: > > Any further comments would be welcomed. There's some disagreement about > the appropriateness of the last section, < > https://github.com/django/django/pull/1463/files#L5R318> so it would be > particularly

Re: Performance optimisation documents, ticket 20877

On Sat, Aug 10, 2013, Daniele Procida wrote: > > >Work in progress; comments appreciated: > Any further comments would be welcomed. There's some disagreement about the appropriateness of