I've got a large computational problem that can be done in small chunks <10sec and where the data required for each portion of the simulation is very minimal.
What I was hoping to do was dump a whole bunch of tasks in a Task Queue and then let the app engine scale up so that it can tear through that queue. Unfortunately i'm running into a problem where if i let the queue run too quickly then my log fills up with stuff like Request was aborted after waiting too long to attempt to service your request. Most likely, this indicates that you have reached your simultaneous dynamic request limit. This is almost always due to excessively high latency in your app. Please see http://code.google.com/appengine/docs/quotas.html for more details. I have a paid account, so it seems that from the quota documents I should be able to consume 72 CPU-minutes/minute - yet when i look in my dashboard it rarely gets much about 3 cpu-seconds/second. Unfortunately if I put shorter requests in the queue then i run into the limit of 20 queue requests per second, and it's more efficient for me to keep my requests in the 10 second range. What's the best way to make this consume more resources at a higher rate? thanks, Graham -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en.
