Hi, I changed my test so it sends a batch of requests every 2 seconds. The batch size starts out as 1 and increases by 1 every x seconds. Last run I did I had it increase by 1 every 100 seconds. This ramped up things slowly.
I still started getting errors around 16-20 requests per second. My dashboard says I don't get anything above 20 requests per second or so. Am I still ramping things up too fast? I'll try an increase of 1 request every 200 seconds a bit later. Thanks On Apr 15, 5:54 pm, boson <[email protected]> wrote: > You need to ramp up your tests over many minutes to allow GAE to spawn > enough instances to handle the traffic. I don't know their exact > algorithm, but I know it takes time to scale up. > > On Apr 15, 1:33 pm, Anonymous Coderrr <[email protected]> wrote: > > > > > 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. > > > On Apr 15, 2:19 am, Barry Hunter <[email protected]> wrote: > > > > 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 <[email protected]> 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--Hidequoted text - > > > > - Show quoted text -- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
