Queues are not tied to a specific instance of your application. Tasks are executed against a free instance of your application.
On 27 May 2011 15:06, stevep <[email protected]> wrote: > I am doing the same as Robert with multiple queues. However, I am > wondering about this with the new pricing. > > Does each task queue get set up as an instance? If so, then I think I > may have to re-architect once the new pricing hits. > > If a task queue is an instance... Much will depend on the scheduler. > If it makes decisions based on overall latency, then we will have to > split slow-fast functions into different queues otherwise very sub- > optimal scheduling decisions are likely. If it makes decisions more > granularly based on intra-module function latency, then bigger modules > (more functions per instance) will be better. Today's need to > segregate slow/fast tasks to avoid throttling (let's assume that is > what causes the slow queue response) suggests an overall latency > evaluation is being used. > > Going back to my original question: If having 3 queues today means > three instance charges in the future, a separate queue for the odd, > low-priority, slow task is likely a very expensive proposition. If the > new scheduler continues to penalize for moving such a task into a > higher priority, fast-functions queue, well then... rock meets hard > place. > > cheers, > stevep > > > ***On May 26, 9:35 pm, Robert Kluin wrote*** >> I can give you some of my observations, maybe they will help a >> little. I occasionally see one queue slow down for no obvious reason, >> because of this when I'm trying to do sustained high-volume stuff I >> spread it over a few queues. It seems to help keep the overall rates >> up. When a queue starts having a lot of tasks fail, that queue seems >> to slow down a bit, but other queues don't (unless the reason it is >> slowing is global, say because of datastore issues). Depending on my >> needs, I like to put 'slow' tasks in their own slow queue. I do this >> because if the latency of the tasks in a queue is high, that queue >> seems to slow down. Obviously for some use cases you might rather mix >> the slow tasks with a lot of fast tasks to prevent any slow downs. > > -- > 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. > > -- Greg Darke -- 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.
