Just did a test of 100 simultaneous hits of the postProcessor with caching in place. First request was about 22 seconds, but subsequent loads required only about 33 ms. One REALLY strange issue which did occur was that every 6th post timed out...in a very nice pattern. Tried this manually but did not have any problem, so this must be related to the density of the hits. Should we be concerned about this?

Re-opening after writing caching for downloads.

this should really be listed as "completed" rather than "fixed".
Will return to this task once we've written code to cache the results of the posts.

For the post test: 50 simultaneous hits crashes the server, so kind of hard to really do any metrics. 10 simultaneous hits was ok.

Load testing of the load custom build page. Summary of results.
Ran 1000 simultaneous hits of this page and looped 10 x (ie. 10,000 hits).

Average time 5.1s, max time 95sec, approx 5% error where errors were timeouts.
Throughput 93 sec.

I did do runs where the error rate was HUGE: 78% once. I think there must have been a server problem at that particular time, but not sure how to tell.