java - GAE Starting dynamic instance to serve requests instead of using idle resident instances -
i ve checked bunch of other post same subject 1 : “resident instance doesn't seem work” couldn t find working answer problem
i have 4 f2 resident , whenever goes application, instead of using resident instance, new dynamic instance mounted answer request. , person attempting use application wait 20 seconds. new requests come new dynamic instance. response time on resident instances inferior min pending latency (5 sec). app in production since yesterday , if no 1 uses 5 minutes next guy connect have wait 20 sec !
from ve read, if set min idle instance 4 ( in order have resident instances) gae try have 4 iddle instances time , ll start new instances; have wait 35 sec first connections after 2 minutes of using application fine. guy working @ google told me there bug in management of resident instances , have have 3 resident instances have quick answer users. m sure haven t understood something. me let users have fair response time when connect application , no 1 have connected 5 minutes please ?
thank much
check gae mailing list on google groups, you'll see question come on , on , on again.
the short answer is, gae designed high loads. resident instances exist handle spikes in workloads, although haven't seen formal definition of "spike". if gae's mysterious load balancing algorithm doesn't determine traffic spike, you'll new dynamic instance.
if throw hundreds or thousands of requests @ app, of them directed resident instances while waiting dynamic instances spin up.
there's not can join long list of people have complained this. there's @ least 2 issues filed against this:
alternatively can rewrite app don't have 20s startup time. there's few things can do, defer of loading, it's painful in java.
as aside, python , go runtimes seem start faster.
Comments
Post a Comment