Ikai - can we assume by your answer that the task queue is in fact impacted by user facing requests? the task queue is setup to handle 40 requests/second, how could you ever get this performance if the instance count is dictated by user requests?
if this is the case, then the only way to get decent task queue performance on a low volume site is to bombard it with small, no-op requests so your app instance count increases. is this just patchwork fixes until the long running processes (from the Roadmap) is complete? On Sep 16, 10:05 am, "Ikai Lan (Google)" <ikai.l+gro...@google.com> wrote: > Jason, I think your situation is fine. Offline tasks have the property that, > unlike user-facing tasks, do not require instant execution. If you schedule > an offline task for "now", that actually means "when there's capacity" and > App Engine can allocate idle capacity to process your request. Thus, the > need to spin up additional instances is unnecessary in most cases. Are you > seeing that your tasks are backed up? > > > > On Thu, Sep 16, 2010 at 12:56 PM, bFlood <bflood...@gmail.com> wrote: > > "which in turn affects the capacity available for running offline > > tasks" - so, if you have a low volume site, you won't get that many > > instances for your tasks? likewise, if you have some user facing > > requests that go longer then 1000ms (by design or otherwise), the > > instances available for your tasks are impacted? or am I confused? > > > On Sep 16, 8:44 am, "Nick Johnson (Google)" <nick.john...@google.com> > > wrote: > > > Hi Jason, > > > > The same appservers are used to serve user-facing and offline traffic. > > The > > > volume of user-facing traffic (that is below the latency threshold) you > > > serve determines how many appservers we provision for your application, > > > which in turn affects the capacity available for running offline (task > > queue > > > and cron) tasks. > > > > -Nick Johnson > > > > On Thu, Sep 16, 2010 at 1:41 PM, Jason C <jason.a.coll...@gmail.com> > > wrote: > > > > The number of instances that App Engine makes available to your > > > > application depends on if you keep your average request time under > > > > 1000ms for user-facing requests. > > > > > Ikai Lan (I believe) said that taskqueue and cron job requests do not > > > > count against this boundary. Ikai also said that this boundary was in > > > > place because longer requests were bad for the ecosystem. > > > > > Since taskqueue and cron job requests do not count against this > > > > boundary, in order for them to not be bad for the ecosystem, I'm > > > > guessing that they are served from a different set of servers than > > > > user-facing requests are. > > > > > We (appid: steprep) have a number of external machines that also hit > > > > our urls. While we make every effort to keep user-facing requests > > > > quick and responsive, we often use many seconds serving the requests > > > > that are built for external machines (by design). > > > > > It has only just struck me this morning that this could be having a > > > > bad (perhaps dramatic) impact on our overall scaleability. > > > > > First off, is it true that cron and taskqueue items are served on a > > > > different set of servers? If so, is there any way to designate that a > > > > particular url is being requested by a machine and can be routed to > > > > this alternate set (of presumably slower) servers (e.g., a request > > > > header)? > > > > > If I'm way off on all of this, and if taskqueue and cron jobs are > > > > served from the same set of servers, I'm not sure how the "bad for the > > > > ecosystem" argument holds, and perhaps Google should revisit this > > > > 1000ms boundary condition altogether. > > > > > -- > > > > You received this message because you are subscribed to the Google > > Groups > > > > "Google App Engine" group. > > > > To post to this group, send email to google-appengine@googlegroups.com > > . > > > > To unsubscribe from this group, send email to > > > > google-appengine+unsubscr...@googlegroups.com<google-appengine%2Bunsubscrib > > > > e...@googlegroups.com><google-appengine%2Bunsubscrib > > e...@googlegroups.com> > > > > . > > > > For more options, visit this group at > > > >http://groups.google.com/group/google-appengine?hl=en. > > > > -- > > > Nick Johnson, Developer Programs Engineer, App Engine Google Ireland Ltd. > > :: > > > Registered in Dublin, Ireland, Registration Number: 368047 > > > Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration > > Number: > > > 368047 > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine" group. > > To post to this group, send email to google-appeng...@googlegroups.com. > > To unsubscribe from this group, send email to > > google-appengine+unsubscr...@googlegroups.com<google-appengine%2Bunsubscrib > > e...@googlegroups.com> > > . > > 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 google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
