<div><div><div class="gmail_quote">On Wed, Mar 11, 2009 at 6:32 PM, mgross <span dir="ltr"><<a href="mailto:markgross@thegnar.org">markgross@thegnar.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On Wed, Mar 11, 2009 at 09:15:10AM -0700, Dylan Reinhardt wrote:<br>
> On Wed, Mar 11, 2009 at 7:34 AM, mgross <<a href="mailto:markgross@thegnar.org">markgross@thegnar.org</a>> wrote:<br>> If you have specific bottlenecks *after* you've done the standard<br>
> deployment/caching stuff, I'd love to hear about them.<br>
<br>
</div></div>I be happy to share, but I was hoping for someone to point out some<br>
for me to use as starting points ;)</blockquote><div><br></div><div>Honestly, I don't know of many. The ORM and templating systems are pretty lightweight and you can swap in different solutions if you want to. The major gripes I've heard are with the architecture of the admin module... but it's optional and typically not used under load anyway.<div>
<br></div><div>The problems I've seen with Django deployments are typically configuration issues. Things like using memcached on a virtual host system where memory is sparse. Or forgetting to turn of the DEBUG flag.</div>
<div><br></div><div><div>That's why I'd love to hear if you encounter any issues. I'm just not aware of that many. </div><div><br></div><div>Dylan</div></div></div></div></div></div>