App Engine will not be leaving preview prior to Sept 26th

199 views
Skip to first unread message

Gregory D'alesandre

unread,
Sep 2, 2011, 2:04:22 AM9/2/11
to Google App Engine group
Hello All, 

I know there has been a lot of speculation that new billing will be taking affect in 2 weeks.  In our notice we said that we'd be leaving preview (which is when new pricing will go into effect) in the second half of September.  I wanted to be a bit more specific and let you all know that App Engine will leave preview no earlier than September 26th.  There are still a number of things left for us to do to be ready to go which is why we don't have a specific date, but we wanted to give you all more precision in the timeframe.

Thanks,

Greg D'Alesandre
Senior Product Manager, Google App Engine

Bay

unread,
Sep 2, 2011, 3:29:02 AM9/2/11
to google-a...@googlegroups.com
While you are working please fix the scheduler.

It needs to be possible for us to force as little as 1 instance at any given time - knowning that the scheduler obviously does not work. 

Even with a setting allowing up to 15s in latency before a new instance is spun up, new instances are being opened and warmup-calls made _all_ the time while no latency goes above 3s.

Raymond C.

unread,
Sep 2, 2011, 4:23:43 AM9/2/11
to google-a...@googlegroups.com
So I would translate it to "new pricing will be effective starting 27th Sept".

Sorry I am not trying to be ridiculous, but thats what you did for announcing price change back at May with so many unknown and now announcing it effective within one month, while most of the issues are still not yet resolved.


Anders

unread,
Sep 2, 2011, 5:30:15 AM9/2/11
to google-a...@googlegroups.com
By having a guarantee of only 1 instance (or any specified max number of instances) we as customers can ensure that our budget isn't suddenly eaten away by spikes of lots of instances being spawned. One potential problem is of course that the application can become extremely slow resulting in a really bad end-user experience. I think Google should be generous and have unlimited free instances. Google will still make a lot of money on the quotas. AND, that will make GAE super competitive. AND, then it would not be a problem with the instances being opaque and Google would be free to adjust the instances as they see fit.

Gergely Orosz

unread,
Sep 2, 2011, 6:31:17 AM9/2/11
to google-a...@googlegroups.com
Could I please ask the GAE team to let us, customers know the exact date when transition will be and make sure we have the tools and a reasonable time frame to get ready for this (e.g. have the scheduler working correctly). Is this too much to ask? I also completely agree with Raymond's comments.

Nick Rudnik

unread,
Sep 3, 2011, 11:45:58 AM9/3/11
to google-a...@googlegroups.com
I agree this scheduler needs a lot of work. I also think Google should not be charging us based on a black box algorithm that we cannot directly control or understand. Any defect or problem in the scheduler will dramatically cost us when it should be Google that pays for any defects like that.

Gopal Patel

unread,
Sep 3, 2011, 12:18:07 PM9/3/11
to google-a...@googlegroups.com
initially I misunderstood the maximum idle instances. it exactly means that. if your app set to 2 idle instance. your app will have as many instances as it needs. but if traffic reduces it will kill rest of the idle instance apart from last two AFTER their 15 minutes cycle over. so if there is a small spike happen which cause four instance to start for only two minutes. you will be charged for one hour since each instance will be on for next 15 minutes. so extra ( 60 - 8 = 52 minutes are charged extra ).  it will not be a problem for high traffic sites which have constant and complete 24 hour smooth traffic instead of spikes.  latency is simple. more latency more profit slower app. less latency less profit faster app.

am I understanding correctly now. ?

On Sat, Sep 3, 2011 at 9:15 PM, Nick Rudnik <nru...@gmail.com> wrote:
I agree this scheduler needs a lot of work. I also think Google should not be charging us based on a black box algorithm that we cannot directly control or understand. Any defect or problem in the scheduler will dramatically cost us when it should be Google that pays for any defects like that.

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

Reply all
Reply to author
Forward
0 new messages