only one
gets resolved.
On Wednesday, 20 February 2013 21:24:02 UTC, Herr Kaste wrote:
>
> Better follow this issue:
> https://code.google.com/p/googleappengine/issues/detail?id=8781
> Google people already replied to that one.
>
> On Tuesday, February 19, 2013 2:42:17 PM UTC+1,
quota to the normal-paid quotas?
>
>
> El martes, 19 de febrero de 2013 14:44:01 UTC+1, Martin Long escribió:
>>
>> It will reset. They just need to wait for your payment to fully clear,
>> and update their systems.
>
>
--
You received this message because you ar
It will reset. They just need to wait for your payment to fully clear, and
update their systems.
--
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-ap
Guys, I'm pretty sure that Google do not monitor this group now that SO is
the support channel. Could you PLEASE go and start the issue at
http://code.google.com/p/googleappengine/issues/detail?id=8844
Also, PLEASE add a comment including your app id. Google don't take issues
seriously unless e
I too am seeing a lot more instances being created. My app is normally
served by a single instance, with a second being invoked maybe 2-5 times a
day, but just spikes. Now it is constantly running around 4-5 instances.
I'm not being billed for them, billing has remained about the same, but it
i
:28:04 UTC, Martin Long wrote:
>
> Indeed, but there seems to be no explanation for the high latency. On
> appstats there is a massive gap before any API calls.
>
> On Thursday, 13 December 2012 02:48:08 UTC, pdknsk wrote:
>>
>> > LOT more requests before it sta
Indeed, but there seems to be no explanation for the high latency. On
appstats there is a massive gap before any API calls.
On Thursday, 13 December 2012 02:48:08 UTC, pdknsk wrote:
>
> > LOT more requests before it starts bumping up the instances. Also, I've
> > notices that the latency on som
Until yesterday my app: rundouble-hrd, ran comfortably within a single
instance, and did so right though our busy summer period. It typically
never breaks the 28 instance hours, unless I trigger a backup.
Yesterday it clocked up 20c or so in instance hours. Now, whenever I look
at the "Instanc
