AppEngine starts new instances without need for them

[Milan Aleksic]

I am a subscriber for "Always On" option on Google AppEngine. I do not understand why does GAE have to start new instances when there are already "Always On" instances that are turned on and that do nothave big number of requests at that time.

This drives me crazy since it nullifies what I get with the AlwaysOn subscription. Any ideas how to fix this behavior? I have latency problems because of this which I wanted to remove by using AlwaysOn. I am thinking of cancelling subscription since it just does not work. 

[Matija]

If any system always checks for every available resources it can't scale up easily. Remember single counter and sharded counters. 

I think that they use sharded counters (or something like that) for instance availability. That is why sometimes they use 'always on' instances and sometimes not. 

[Ikai Lan (Google)]

Do you have "threadsafe" set to true? If you do not, each instance will only handle a single request at a time.

Ikai Lan 
Developer Programs Engineer, Google App Engine

Blog: http://googleappengine.blogspot.com 

Twitter: http://twitter.com/app_engine

Reddit: http://www.reddit.com/r/appengine

--
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-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

[Milan Aleksic]

Hi,

I moved to 1.4.3 (from 1.4.2), added threadsafe element... and I
believe after couple of hours of testing that you just solved my
issue!
Thanks for clearing up this behavior!

Milan Aleksic
http://www.milanaleksic.net

On May 4, 10:24 pm, "Ikai Lan (Google)" <ika...@google.com> wrote:
> Do you have "threadsafe" set to true? If you do not, each instance will only
> handle a single request at a time.
>
> Ikai Lan
> Developer Programs Engineer, Google App Engine
> Blog:http://googleappengine.blogspot.com
> Twitter:http://twitter.com/app_engine
> Reddit:http://www.reddit.com/r/appengine
>

> On Wed, May 4, 2011 at 1:39 AM, Milan Aleksic <milanalek...@gmail.com>wrote:
>
>
>
>
>
>
>
> >  I am a subscriber for "Always On" option on Google AppEngine. I do not
> > understand why does GAE have to start new instances when there are already

> > "Always On" instances that are turned on and that *do not*have big number

> > of requests at that time.
>
> > This drives me crazy since it nullifies what I get with the AlwaysOn
> > subscription. Any ideas how to fix this behavior? I have latency problems
> > because of this which I wanted to remove by using AlwaysOn. I am thinking of
> > cancelling subscription since it just does not work.
>

> > <http://i.imgur.com/jVgta.png>