Good points.
I rewrote the test so it fires off 20 requests from 20 distinct ip
addresses simultaneously, once a second 10 times.
In effect 20 concurrent requests, once a second.
I had about 15% loss and the request time degradation was there. (2
seconds to fulfill a request on an idle system, 15 seconds under
load).
This still is no where near advertised load rates.
> One thing that has become apprent is appengine, is designed to scale
> under real world usage.
>
> So if your App went from 0/1 users to 500 in a matter of seconds, then
> the system wont work well. You need to ramp up the usage slowly.
>
> Even a slashdotting would result in a 'ramp' usage.
>
> Also 500 users coming from once source, might be a bit suspicios, and
> appengine could be weary of a DOS attack.
>
> On 15/04/2009, Anonymous Coderrr <
greedw...@gmail.com> wrote:
>
>
>
>
>
>
>
> > I have a fairly simple app - it looks up a couple of objects from the
> > google datastore and then creates a page from django template - pure
> > vanilla.
>
> > I wanted to see how my app would perform under heavy load, so I set up
> > a simulation where 500 virtual web-browsers would attempt to request
> > my page twice - exactly at the same time.
>
> > The results were dismal!! Nearly 50% of the requests resulted in a
> > "HTTP response code: 500" from GAE - not my application, but
> > apparently GAE itself.
>
> > I check my dashboard logs - no errors from my application. No errors
> > anywhere I could find.
>
> > What can I do? I'm not expecting 500 requests per second, but
> > certainly maybe 100. The best rate I can get according to the
> > dashboard is about 4.5 requests per second. The dev server running on
> > my laptop does better than that!!!
>
> > Thanks
>
> --
> Barry
>
> -www.nearby.org.uk-www.geograph.org.uk-- Hide quoted text -
>
> - Show quoted text -