Should developers pay for the useless instances? Can we set max instances to 1?

[Sun Jing]

My site usually has little traffics. But app engine launched many useless instances that caused I ran out of quotas yesterday.

I had already set Max Idle Instances to 1 and Min Pending Latency to 15s, but it didn't prevent app engine to waste my quotas.

I think it's unfair for me to pay for that. It's clear that I should only pay for the instances marked "Billed" in the charts.

If Google thinks I should pay for your mistake, please let me be able to set max instances to 1 to avoid the waste.

[Nikhil Jain]

Is this M/S or HR App.?

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

[alex]

What's the point in using AE infrastructure then? You're probably better off to EC2 micro instance, or openshift, or cloudfoundry, or appfog, or heroku, in that case.

Personally, I'd be -1 unstarring (if I could) such a feature.

[Robert Fischer]

I can see how this feature would be useful -- especially for testing.

I have an app I haven't released yet that once a minute sucks in new data and spawns many (maybe up to 200/minute max) requests using the task queue to process that data. When using frontends I was often spinning up 2-3+ instances automatically even when throttling back task queue rates. I can run all of the requests on the same size backend (B1) just fine, the only downside is that I'm paying $1.20 a day now to have a test app running 24/7...

I am using backends (one B1 backend specifically) for the sole purpose of being able to control how many instances are running (only one). My requests should work great with multi-threading (using python 2.7 w/ HR) and are neither long running or latency critical but I'm using a backend because it's cheaper than letting frontends spin up and run idle.

-Robert

On Tue, Jul 10, 2012 at 11:06 PM, alex <al...@cloudware.it> wrote:

What's the point in using AE infrastructure then? You're probably better off to EC2 micro instance, or openshift, or cloudfoundry, or appfog, or heroku, in that case.

Personally, I'd be -1 unstarring (if I could) such a feature.

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.

To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/Ecu4sDu46WkJ.

[Sun Jing]

I'm using M/S datastore. I think HR may be better, but I don't want to migrate now.

[Rerngvit Yanggratoke]

The feature can be optional, right? People who want unbounded number of instances can disable that feature. To me, it doesn't make sense that it is impossible to limit number of active instances when you are paying for that.

On Wed, Jul 11, 2012 at 8:06 AM, alex <al...@cloudware.it> wrote:

What's the point in using AE infrastructure then? You're probably better off to EC2 micro instance, or openshift, or cloudfoundry, or appfog, or heroku, in that case.

Personally, I'd be -1 unstarring (if I could) such a feature.

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.

To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/Ecu4sDu46WkJ.

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.

--
Best Regards,
Rerngvit Yanggratoke 

[Kyle Finley]

Here's the feature request. Please star it.

http://code.google.com/p/googleappengine/issues/detail?id=5858

[Michael Hermus]

Starred. IMO there is absolutely no good reason to NOT allow people to set a maximum number of instances.

I personally would not use such a setting for a production app that expects variable traffic spikes, but GAE is not just for apps that need to scale infinitely. Sure, that is one of its most powerful features, but simply avoiding all infrastructure management, at whatever scale, is a huge value.