A model where front-end instances are focused on latency sensitive requests and backends are reserved for jobs that have no strict latency requirements will scale better. Imagine a case where your "max idle front-end instances" is set to 1, and you run a 2-minute long cron job on a front-end. During those two minutes, every request destined for a front-end could potentially cause a new instance to be created, causing large latency spikes under load. For apps where initialization times are large, compared with request processing times, this won't scale at all.
On Wed, Nov 16, 2011 at 12:00 PM, Simon Knott <[email protected]> wrote: > Why don't you just use a cron job against front-end instances? Cron jobs > can last 10 minutes. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/XIEW58_YyJMJ. > > 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.
