My 2 cents: - queues scale up very well: I tried them with no throttle (on bucket size) and you easily get 12-15 jvm running your computations. To my knowledge, queues are the best way to get parallelism on GAE. but - data access / contention may be the issue: don't you write anything back ? That may become the issue after your big computations have run. You may have write contentions then unless you use sharding.
We may provide more feedback but you have to disclose more on what you want to achieve. regards didier On Mar 7, 4:15 pm, Simon Knott <[email protected]> wrote: > A few thoughts: > > - Are you taking into consideration loading requests? These will cause > pauses which can last a few seconds. > - Have you enabled warm-up requests? > - What do your logs say are causing the 5xx errors? > - Have you looked at the logs for what may be causing the long pauses? > i.e. are they delays caused by communications between your test PC and the > app, or entirely within the GAE app? > - It's very easy to set up task queues to give you the same stats and > give you a comparison - personally it sounds like task queues would be a > good fit for your requirements, based on the slightly vague information! -- 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.
