To paraphrase johnP, "This afternoon is a serving train-wreck."
My poor unicorns' tongues are raw from gorging on Sour Skittles(tm).
David
On Friday, March 1, 2013 7:32:29 PM UTC-7, Cesium wrote:
>
> I'm sure you noticed the question on this forum that Takashi did respond
> to.
>
>
> On Frida
I'm sure you noticed the question on this forum that Takashi did respond to.
On Friday, March 1, 2013 11:47:21 AM UTC-7, Carl Schroeder wrote:
> I am porting to Go. Then I care much less about the instance scheduler
> committing unicorn genocide.
> Almost done.
>
>
> RIP GAE/J, thanks for was
I am porting to Go. Then I care much less about the instance scheduler
committing unicorn genocide.
Almost done.
RIP GAE/J, thanks for wasting my dev time replacing you!
On Friday, March 1, 2013 9:28:13 AM UTC-8, johnP wrote:
>
> This morning is a serving train-wreck here, too.
>
>
>
>
> On W
This morning is a serving train-wreck here, too.
On Wednesday, February 27, 2013 7:50:47 AM UTC-8, Kinesh Patel wrote:
>
> On Python 2.7 paid app. Setting an idle instance seems to mitigate this,
> but every time a new dynamic instance is spawned or hit i get this problem.
> Definitely not n
I have sacrificed several unicorns and prayed fervently to the Google Gods,
but this morning instances are thrashing badly; living no more than a
minute or so.
Google really needs to figure out the underlying issue, and also start
communicating with their customers more effectively. The awesome
Hello Takashi,
any feedback for us?
Cheers
Mos
On Thu, Feb 28, 2013 at 1:06 PM, Mos wrote:
> Trust me; Google has no clue what's going on.
> The instance scheduler went crazy, people have downtimes and have
> increased billing (for weeks!)
>
> If Google would be able to track the problem (or wo
Mos makes some good points and states them clearly.
However, my idea of Faith Based Scheduler Maintenance seems to be yielding
pretty good results.
David
On Thursday, February 28, 2013 5:06:00 AM UTC-7, Mos wrote:
> Trust me; Google has no clue what's going on.
>
> The instance scheduler we
+1 to Mos
Trust me; Google has no clue what's going on.
The instance scheduler went crazy, people have downtimes and have
increased billing (for weeks!)
If Google would be able to track the problem (or would have a clue how
to fix it),
they would give a comment.
As I wrote. That's not the first t
Trust me; Google has no clue what's going on.
The instance scheduler went crazy, people have downtimes and have
increased billing (for weeks!)
If Google would be able to track the problem (or would have a clue how
to fix it),
they would give a comment.
As I wrote. That's not the first time. Last
Many apps are hitting the same issue, starring the following may increase
chances of getting resolution. The app engine performance is unpredictable.
Right now, as far as we are concerned, the most effective solution is to
offer prayers very sincerely every morning.
http://code.google.com/p/google
A couple hours later, all is well.
Instances are lasting.
Latency is low.
Thank you Mr. Sparkles. (burp).
On Wednesday, February 27, 2013 6:45:50 PM UTC-7, Cesium wrote:
> Oh Joy,
>
> Now the console charts have been erased.
>
> I'm losing it.
>
> Unicorn liver pate for dinner.
>
> David
>
Oh Joy,
Now the console charts have been erased.
I'm losing it.
Unicorn liver pate for dinner.
David
On Wednesday, February 27, 2013 6:10:37 PM UTC-7, Cesium wrote:
> Starting about 16:30 Pacific time, my Java HRD Instances were shutting down
> after just a few seconds.
>
> Just as my rage
Starting about 16:30 Pacific time, my Java HRD Instances were shutting down
after just a few seconds.
Just as my rage reached class IV, serving returned to normal.
I know this is an overreaction, but I may have to sacrifice a unicorn.
Please, please, App Engine team, spare Mr. Sparkles.
This
I'm also getting this problem.
On Wednesday, February 27, 2013 7:50:47 AM UTC-8, Kinesh Patel wrote:
>
> On Python 2.7 paid app. Setting an idle instance seems to mitigate this,
> but every time a new dynamic instance is spawned or hit i get this problem.
> Definitely not normal behavior.
--
Y
14 matches
Mail list logo
