0

Since GAE will create a new instance which would cause latency when there is no one, we'd like to find a method to have an instance which will always be there when we need it.

We use cron + auto scaling just like the method mentioned in the answer here: Google App Engine - automatic-scaling with always on instance?

Our problem is that if we say there is already an instance A which was created by the cron task on GAE. We expect that GAE will use the instance A to handle the following post. However, when there comes a post, GAE will create an instance B and process the following post by instance A. The instance B seems redundant. Since we would like to avoid over the daily quota, is it possible to process the post by instance A if there is not much traffic?

Community
  • 1
  • 1
Jean Lin
  • 159
  • 1
  • 2
  • 8

1 Answers1

0

GAE will not create a new instance if your first instance is not overloaded. Each instance can handle quite a few requests simultaneously - especially if they do not do anything except for keeping the instance up.

MeLight
  • 5,454
  • 4
  • 43
  • 67
  • Thank you for your answer. We create another project and it works as you said. Do you have any idea about why our first project has that problem? – Jean Lin May 05 '17 at 02:30
  • Np. I can't think of something that can cause this type of behavior. – MeLight May 08 '17 at 08:09
  • we found out that this problem just gone away and have no idea how it fixed. anyway, thank you for your information – Jean Lin May 22 '17 at 05:50