Also, you should really give Go a try. It's amazing how fast you can process data (including images) comparing to Python or Java. Plus, your loading requests will be 10x faster. Obviously, RPC calls to App Engine services will be the same though.
On Fri, Nov 23, 2012 at 10:52 AM, alex <[email protected]> wrote: >> When Analyzing a large body of text you can't really "chunk" the task. >> While chapter marks kind of work, not really. > > Store intermediate data in memcache/datastore/task post body and re-enqueue. > >> Same for image processing, we do shape detection and trim large images you >> can't "chunk" the task. > > Agree but this seems like the right job for a dynamic/static backend. > I'd create a separate app to do just that if I needed all 20 backends, > i.e. a lot of load. But, I wouldn't let users launch it directly, but > enqueue from another app. If it 503, temporary store somewhere to try > enqueue again. > >> >> >> -- >> 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.
