Elf Sternberg

If you need that kind of performance, you're probably better off writing your own advanced extra(select=) pairings to contain the entirety of the SQL in a single call.

Django 1.2 seems to be much better at avoiding this kind of nonsense.

Also, I've discovered that if your querysets are lazy but even constructing is expensive, you can still avoid the construction costs when they're not needed by crafting a constructor into a functor or closure that doesn't get triggered until invoked by the template handler.

[Edit: Wow, that last paragraph is so buzzword-compliant, if I were hearing it from someone else I couldn't be sure if they were bullshitting me or not.]