Hey Greg,
Will we be able to adjust the scheduler for each version of our
application? Two use-cases come to mind: 1) different options for
Python / Go / Java versions of an app, and 2) different options for
'front-end' versions serving user traffic and processing tasks. Would
be nice so that
For instance, for a B4 (approx 2.4GHz) instance: consuming 10
Mcycles/request = 240 request/second/Instance, 100 Mcycles/request = 24
request/second/Instance, etc.
We are only planning on having one size of Frontend Instance.
Q: So, is a Frontend Instance going to be a B4?
Even if the CPU is
Hi!
Under the new model for the Datastore API calls, does it mean that I don't
care anymore about performing operations in batches? So in terms of costs
db.get(key1); db.get(key2) is essentially the same as db.get([key1, key2])?
Thank you!
On 18 May 2011 07:49, Gregory D'alesandre
Hi Greg,
Can you raise On-demand Frontend Instances free quota to 25 Instance Hours
per day?
The small apps have very low traffics in average, but sometime (maybe
several minutes) it may use more than 1 instances to handle burst traffics,
so that they will got OverQuotaErrors at the end of the
On Wed, May 18, 2011 at 1:57 AM, 风笑雪 kea...@gmail.com wrote:
Hi Greg,
Can you raise On-demand Frontend Instances free quota to 25 Instance Hours
per day?
The small apps have very low traffics in average, but sometime (maybe
several minutes) it may use more than 1 instances to handle burst
Hey Maxim,
Batch calls can reduce your latency allowing your app to service
requests much faster -- so batching is still going to be a good idea.
Also, be sure to check out the async db methods, they can help reduce
latency even further.
Robert
On Wed, May 18, 2011 at 02:54, Maxim
Hi Robert,
Thanks for the clarification.
On 18 May 2011 18:18, Robert Kluin robert.kl...@gmail.com wrote:
Hey Maxim,
Batch calls can reduce your latency allowing your app to service
requests much faster -- so batching is still going to be a good idea.
Also, be sure to check out the async
On Tue, May 17, 2011 at 10:13 PM, Robert Kluin robert.kl...@gmail.comwrote:
Hi Greg,
I'm looking forward to seeing the scheduler improvements in the
coming weeks. Overall this looks promising, I'm actually pretty happy
to see that the API calls 'with checks' will be included and just
On Wed, May 18, 2011 at 1:57 AM, 风笑雪 kea...@gmail.com wrote:
Hi Greg,
Can you raise On-demand Frontend Instances free quota to 25 Instance Hours
per day?
The small apps have very low traffics in average, but sometime (maybe
several minutes) it may use more than 1 instances to handle burst
Hello All!
As you've likely heard, when Google App Engine leaves Preview in the second
half of 2011, the pricing model will change. Prices are listed here:
http://www.google.com/enterprise/appengine/appengine_pricing.html. But that
leaves a lot of questions unanswered, this FAQ is intended to
Hi Greg,
I'm looking forward to seeing the scheduler improvements in the
coming weeks. Overall this looks promising, I'm actually pretty happy
to see that the API calls 'with checks' will be included and just
billed by time consumed. Is the 4x cost relative to a master-slave
(M/S) or
Greg,
Still not clear on the datastore costs. For this you say, This means
the cost of your queries will be tied exclusively to the size of your
result set. Is this the same whether you return just the keys (keys
only query) or also the entities. It seems like it should not be the
same since a
12 matches
Mail list logo
