>Instances Die when they reach memory limit. What kind of memory usage are
we talking about here do you have a link 

You are on F1 Instances if you are running on a free app so 128m

>when they get bored OK hense the idea of a cronJob to ping it... 



What if you have a user, and you ping and cause a second instance to Spin
up? You might run out of free quota.


>when they reach an age limit. So an instance in use could be terminated and
a new one started at random times ? Is this documented ?



Nope, but if you check a big apps instances you won't find many that are as
old as the last code update.


>so when the scheduler decides you need 180 instances and you only need 1
What do you mean by this scheduler deciding to create 180 instances of my
app ?



The task scheduler that scales up and down your app sometimes goes wonky,
you only pay for in use instances but I often have 40+ instances when I'm
only using 4.


>I know what I am talking about is a bit of a hack but can this work ? I had
a look at memcache but for some reasons I don't think it can serve me... 

Memcache does almost exactly what you were asking about. But It also
mysteriously resets at any given moment with out warning.  You can go "Write
to memcache" and have the next line be "read from memcache" and your entity
could be gone. Not often, but it can happen.

But 500 instances all share memcache so if you say Value=X they will all
know it to be true instantly.






-- 
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.

Reply via email to