instances are spinning - how to specify fixed instances.

[Rajesh Gupta]

Hi,

We are in the process of looking at our latency issues

  

In this context, it is becoming very difficult, because the instances are spinning and getting killed.

So, we don't have the logs of the which instance are serving the request, because the instances are shutdown immediately, and if we go into the instances screen, the new instances are showing, and the old instances are not shown, and hence the 'view logs' link is not available for the killed instances.

Is there any way to say that do not spin any instances at all, other than the fixed set of instances.

--

Rajesh

www.VeersoftSolutions.com

www.AccountingGuru.net

Accounting/Inventory/Orders on Google Cloud Platform and Mobile

[Rajesh Gupta]

I have the following in the appengine-web.xml

 

   <instance-class>F1</instance-class>

<automatic-scaling>

   <min-idle-instances>2</min-idle-instances>

   <max-idle-instances>2</max-idle-instances>

   <min-pending-latency>10s</min-pending-latency>

   <max-pending-latency>10s</max-pending-latency>

</automatic-scaling>

Attached is the screenshot, and it shows 3 instances.  I have not issued any traffic, and yet shows 3 instances, instead of 2 instances.

[Nick (Cloud Platform Support)]

Hi Rajesh,

This is a specific technical question, not a general discussion of the platform / services and so is off-topic for this forum. It would be better for you to post this question to stackoverflow. Not only will it be on-topic there, but there are a lot more people who will see it and potentially help out.

As to your specific question, when you post to stackoverflow, be sure to include as many relevant details as possible. What kind of work is the instance doing? As far as your logs, you don't need to click an instance to see the logs, and you should simply go to "Monitoring > Logs" in the new Developers' Console, which you should be using anyway, since it is under active development, while the old console is not.

So, I wish you the best of luck in proceeding to open your question on stackoverflow. You can post the link back here and I'll be happy to help comment on the question.

Sincerely,

Nick

On Friday, August 14, 2015 at 6:34:44 AM UTC-4, Rajesh Gupta wrote:

I have the following in the appengine-web.xml

 

   <instance-class>F1</instance-class>

<automatic-scaling>

   <min-idle-instances>2</min-idle-instances>

   <max-idle-instances>2</max-idle-instances>

   <min-pending-latency>10s</min-pending-latency>

   <max-pending-latency>10s</max-pending-latency>

</automatic-scaling>

Attached is the screenshot, and it shows 3 instances.  I have not issued any traffic, and yet shows 3 instances, instead of 2 instances.

[Alex Martelli]

As a general tip, don't specify both kinds of parameters to automatic scaling: the ones trying to reduce costs (max_idle_instances, min_pending_latency) and the ones trying to reduce latency/improve scalability (min_idle_instances, max_pending_latency). We'll have a future blog post about that but that will be a while coming -- for now, I just quote the key take-away from that post -- "Attempting to control for both cost and latency can leave you application in a sub-optimal state, causing it to perform in ways you might not expect."

On Fri, Aug 14, 2015 at 3:34 AM, Rajesh Gupta <rajesh...@veersoftsolutions.com> wrote:

I have the following in the appengine-web.xml

 

   <instance-class>F1</instance-class>

<automatic-scaling>

   <min-idle-instances>2</min-idle-instances>

   <max-idle-instances>2</max-idle-instances>

   <min-pending-latency>10s</min-pending-latency>

   <max-pending-latency>10s</max-pending-latency>

</automatic-scaling>

Attached is the screenshot, and it shows 3 instances.  I have not issued any traffic, and yet shows 3 instances, instead of 2 instances.

On Fri, Aug 14, 2015 at 3:30 PM, Rajesh Gupta <rajesh...@veersoftsolutions.com> wrote:

Hi,

We are in the process of looking at our latency issues

  

In this context, it is becoming very difficult, because the instances are spinning and getting killed.

So, we don't have the logs of the which instance are serving the request, because the instances are shutdown immediately, and if we go into the instances screen, the new instances are showing, and the old instances are not shown, and hence the 'view logs' link is not available for the killed instances.

Is there any way to say that do not spin any instances at all, other than the fixed set of instances.

Yes, it's called manual scaling (as opposed to automatic scaling, which is the default and what you're using above). 

See https://cloud.google.com/appengine/docs/java/modules/#Java_Instance_scaling_and_class (and remember that if you switch to that the instance class must also be switched, from F1 to B1 -- same characteristics, except for the different approach to scaling).

HTH,

Alex

 

--

Rajesh

www.VeersoftSolutions.com

www.AccountingGuru.net

Accounting/Inventory/Orders on Google Cloud Platform and Mobile

--

Rajesh

www.VeersoftSolutions.com

www.AccountingGuru.net

Accounting/Inventory/Orders on Google Cloud Platform and Mobile

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/CA%2BS7ijYOUAXxON5dZ0Gdd6oY%2BgjXRG5QcOV7SupMyv4tPccrgQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.