Alternatively break processes in separate operations and call those via Fetch, but put the data in to the same mem-cache or data store.
Primary app Fetches 2 or more sub processes, and the data from each goes in to a data store. This allows you to have multiple threads, and you won't hit ram limits because you will be running more than one instance. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Norlesh Sent: Saturday, December 25, 2010 4:03 PM To: Google App Engine Subject: [google-appengine] Re: Billing for additional RAM Another thing to consider is using a separate service for doing the heavy lifting in the background. In "Google I/O 2009 - App Engine Nitty-Gritty: Scalability, Fault Tolerance, and Integrating Amazon EC2" [http://www.youtube.com/watch? v=p4F62q1kJ7I] they use a dedicated server instance on EC2 to do all there heavy lifting in the background. Definitely not ideal but an option. Shane -- 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.
