Whether the edge cache works or not, you can bet that Google will eventually figure out how to stop you from effectively DOSing the system without paying for it :-)
This is a really fun problem to solve though. Jeff On Fri, May 20, 2011 at 2:34 PM, Chris Farmiloe <[email protected]> wrote: > I do know that the scheduler is certainly not instant. So serving it > dynamically via instances doesn't sound the solution. > From zero to thousands of QPS is going to take some time for the scheduler > to realize what is happening (like longer than 10mins) how fast is the > traffic really going spike? > Having the edge proxies cache it is the only hope, but there is no control > (or even guidelines) on how these work or if they might just start ignoring > you if you are killing them. > Sounds fun! > > -- > 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. > -- 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.
