Apache flood is a…reasonable load tester for HTTP servers.Â You give it an xml files which says “get this page then this one then this one” then spawn some processes to do so.Â A little bit non user friendly, as I was never able to get the tests to really…run the way I expected them to.Â Turns out that installign apache flood has some…difficulties, but is not too bad.Â Here is my post on it in case others run into the same difficulties.Â Let me know if you have any feedback on this!

Well it seems that you can’t do ‘generic’ queires from within a template — the only reason being as I can tell– that functions don’t take parameters when you call them from within a tempalte. Pity.

Therefore the way to query within a template is to make a ‘helper function’ that will do your query for you, if possible.

I think. According to this post
* Attribute access of a related object which hadn’t previously been
accessed (and select_related will work around that for you so you get
all the queries up-front).
* Method accesses which fetch data (these should be documented in your models).
* Template tags which execute SQL (these should be documented in the
template tags which are executing the SQL).

As django auto forms seem to not do anything except ‘many to many’ relationships yet (yeck) and, with foreign keys you probably don’t want the visitor just setting those anyway, you are left to use an autoform but ‘fill in’ bits and pieces of this ‘partial’ autoform for the user before saving it.

One way to do it is this (uses ‘editable=false’) to not display certain (necessary) things for the user