This isssue has been covered on other posts -- with no clear answer.
(see:
http://groups.google.com/group/google-appengine/browse_thread/thread/88cde75072a08fc2/56b80e93e40ce3dd
and
http://groups.google.com/group/google-appengine/browse_thread/thread/1c8dd575aa6804c2/e84294dc934a1500
for referenc
+1
Thanks googlers! This is awesome.
On Nov 7, 4:58 pm, nickmilon wrote:
> + 1
> Impressive performance gains - congratulation to Google and App Engine
> team.
> Lets hope current performance will be a benchmark for the future.
>
> On Nov 7, 12:17 am, Greg wrote:
>
>
>
>
>
>
>
> > Check out the
Wow, I second lennysan. Awesome postmortem! Thank you so much for
sharing it with us.
Marc
On Mar 5, 12:25 pm, lennysan wrote:
> I've been working on a Guideline for Postmortem Communication, and ran
> this post through the
> guideline:http://www.transparentuptime.com/2010/03/google-app-engine-
Hi David,
I don't have a precise answer, but I think you are going in the right
direction. The idea is to minimize the response time of your most
popular requests using memcache. Try to cache the html pages derived
from the datastore queries. It is easy to drop the request time to a
few hundred ms
Hi Waleed,
You are not seeing any errors/warnings in the logs? There are a few
possibilities here.
If the request hits your app:
* You could be hitting the 30 seconds limit (maybe because the input
is too large or something). You should see an error in the logs.
* Your code could also be raising
Thanks for you help Eli! I didn't know about the unique name feature.
I will use that trick, at least for the most important crons. Still, I
wonder why I see this failure if my requests / seconds is never higher
than 3 in my dashboard. I mean, if I saw spikes close to 30 at least I
could start debu
ntities and putting them in batches? Does
> each task put() new entities? or are they sometimes putting an entity that
> may already exist?
>
> More info is more better for help.
>
> On Fri, Feb 26, 2010 at 3:35 PM, Marc Provost wrote:
> > Ok, here's my situation:
&g
Ok, here's my situation:
* I use the java implementation and my app id is poolfana.
* I have a bunch of cron jobs scheduled at night (Eastern Time)
* They are all very much parallelized. I am being very strict: they
spawn tasks that only write to one entity each. Each tasks will
execute in a few h
Hi AJ,
Here's a few tips from my experience:
* If your application currently does not have much traffic, most of
your requests will be "loading requests". This could explain the
randomness your are seeing. The app engine needs to load and prepare
your application to handle a request. In my applic
This is a wild guess, but maybe they need to prevent people from
"externally" scheduling cron jobs at a faster rate than what is
allowed. Currently, cron jobs can be executed at most every minute,
allowing a refresh to bypass that limit would allow an external server
to schedule cron jobs at a fast
Hi Alex,
This is a known issue. Check out this thread for discussion +
workarounds:
http://groups.google.com/group/google-appengine-java/browse_thread/thread/3affdf1441f864b6
Marc
On Feb 12, 3:55 am, Alexander Arendar
wrote:
> Hi guys,
>
> yesterday I was trying to model a simple forum comment
Hi everybody!
I am using the java implementation and seeing the following error
logged sporadically, both in the development server and live. Note
that it does not seem to be a "real" error, as the commit always goes
through and my data looks perfectly fine. Could it be a low-level
exception that
ning time 4-5s)
I'm still experimenting with this, I will let you know if I'm able to
reduce the error rate of Task A. I'm currently splitting all my tasks
so that each of them writes to only one entity (before I would split
them in groups of 30-40).
Jason (Google), what are your th
ning time 4-5s)
I'm still experimenting with this, I will let you know if I'm able to
reduce the error rate of Task A. I'm currently splitting all my tasks
so that each of them writes to only one entity (before I would split
them in groups of 30-40).
Jason (Google), what are your th
ning time 4-5s)
I'm still experimenting with this, I will let you know if I'm able to
reduce the error rate of Task A. I'm currently splitting all my tasks
so that each of them writes to only one entity (before I would split
them in groups of 30-40).
Jason (Google), what are your th
This issue driving me crazy! I have cron jobs that must run overnight
and
I started to see this pattern about 3-4 weeks ago. I had to run the
jobs multiple times and
I still have to check them every morning, because sometimes all of
them failed (with the same duration as you guys). Also,
I get this
This issue driving me crazy! I have cron jobs that must run overnight
and
I started to see this pattern about 3-4 weeks ago. I had to run the
jobs multiple times and
I still have to check them every morning, because sometimes all of
them failed (with the same duration as you guys). Also,
I get this
17 matches
Mail list logo
