My reads are serial because there is some dependency on earlier reads.
But the main point is that it was working fine before.
The allowed capability of the current appengine platform is different from
the allowed capabilities of, say, last week's platform.
To have the platform's capabilities
I totally agree with you. It is very difficult to design around the
large variations in performance; more consistency would make me happy
as well.
I try to leave lot of room for latency spikes in my designs and
optimize my data designs to minimize RPCs, but that is sometimes very
difficult.
My HR instances are fine, but those in M/R are completely down
On 25 February 2011 10:57, Robert Kluin robert.kl...@gmail.com wrote:
I totally agree with you. It is very difficult to design around the
large variations in performance; more consistency would make me happy
as well.
I try to
*To:* google-appengine@googlegroups.com
*Subject:* Re: [google-appengine] Re: Experiencing major timeout issues
right now
That's a very important observation and thank you David for letting us know
that. Can other HR users confirm this as well?
On Fri, Feb 25, 2011 at 12:34 PM, David Mora dla.m
@googlegroups.com] *On Behalf Of *Jeff Schwartz
*Sent:* Friday, February 25, 2011 10:18 AM
*To:* google-appengine@googlegroups.com
*Subject:* Re: [google-appengine] Re: Experiencing major timeout issues
right now
That's a very important observation and thank you David for letting us
know that. Can other HR
No, I'm not using HR.
On Thu, Feb 24, 2011 at 2:50 AM, Kaan Soral kaanso...@gmail.com wrote:
It wasn't clear that Jeff is using HR, I wish he doesn't
On Feb 24, 5:24 am, Raymond C. windz...@gmail.com wrote:
So switching from M/S to HR would not help?
--
You received this message because
So i left 2 monitors running doing random inserts and 5 others doing location
queries (geobox). After 6 hours has been an steady line with only 1 error.
Im going to keep it running 2 more days and post the results ( im also running
out of cpu since is a free acount)
Sent from my iPhone
On Feb
My app is still not running normally.
Before, I could do 30-40 datastore reads (in a particular section of
my code) without timeouts.
Now, I can't. It consistently gets timeout errors.
I changed my code to reduce the number of datastore reads to about 5
reads in that section of code, and the
Are you doing those reads in a batch or serially?
Robert
On Thu, Feb 24, 2011 at 12:05, Dennis dennisf...@gmail.com wrote:
My app is still not running normally.
Before, I could do 30-40 datastore reads (in a particular section of
my code) without timeouts.
Now, I can't. It consistently
Same here:
1. 2011-02-23 05:22:13.471 /lmv/Authentication 500 10874ms 0cpu_ms 0kb
On Wed, Feb 23, 2011 at 9:00 AM, Kaan Soral kaanso...@gmail.com wrote:
I am wondering that too
On Feb 22, 6:02 am, David Mora dla.m...@gmail.com wrote:
is this happening also for HR users?
On 21
I am wondering that too
On Feb 22, 6:02 am, David Mora dla.m...@gmail.com wrote:
is this happening also for HR users?
On 21 February 2011 21:51, Dennis dennisf...@gmail.com wrote:
I'm still experiencing timeout issues and have been for over 12 hours.
Simple pages in my application work,
So switching from M/S to HR would not help?
--
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-appengine@googlegroups.com.
To unsubscribe from this group, send email to
It wasn't clear that Jeff is using HR, I wish he doesn't
On Feb 24, 5:24 am, Raymond C. windz...@gmail.com wrote:
So switching from M/S to HR would not help?
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email
Here's my heartbeat log, last number is seconds, it normally takes 0.3
seconds, started going wrong at 13:48, 18 minutes ago.
2011-02-21 13:48:09 0.314763
2011-02-21 13:48:20 0.326129
2011-02-21 13:48:20 0.326129
2011-02-21 13:48:40 10.359252
2011-02-21 13:48:40 10.359252
HTTP Error 500: Internal
I see a lot of datastore timeouts. Seems this is the issue after last major
SDK update. nothing was changed in my code...
I don't know if High Replication datastore may help. Any ideas? (anyway..
moving 190Gb of data will cost a lot)
URI Count % Errors last 6 hrs
There was also a large datastore put spike around the same time. I
noticed significant increases in both get and put timeouts around that
time across several apps.
http://code.google.com/status/appengine/detail/datastore/2011/02/21#ae-trust-detail-datastore-put-latency
Robert
On Mon, Feb
is this happening also for HR users?
On 21 February 2011 21:51, Dennis dennisf...@gmail.com wrote:
I'm still experiencing timeout issues and have been for over 12 hours.
Simple pages in my application work, but the pages that do 30-40 gae read
operations are consistently timing out (they were
I'm still experiencing timeout issues and have been for over 12 hours.
Simple pages in my application work, but the pages that do 30-40 gae read
operations are consistently timing out (they were never a problem before).
Just adding my data point in case others are experience this.
Both gae
18 matches
Mail list logo
