Hi Peter,
Basically your understanding is correct. I conclude my experience
about tuning against the high CPU quota here:
1. Don't care about the Admin Console warning too much. It said you
will exceed quota soon for your red requests, but it never happen. So
just look at your warning logs. I
Hi,
Basically your understanding is correct. I conclude my experience
about tuning against the high CPU quota here:
my own app gives the high amount of CPU error when it hits the root
of the app. I can think of this:
1. py files are probably getting compiled after the app is uploaded
2. a
Agree with you, man, CPU quota error is frequently for me, but just
some query action for less than 100 records, for a python environment,
we need more CPU power than static processing ability, so I think the
way of the limitation should be adjusted.
On Sep 21, 7:27 pm, mitnickcbc [EMAIL
On Sep 26, 1:48 am, mitnickcbc [EMAIL PROTECTED] wrote:
Some update about my latest findings. And these are my guesses, please
do correct me if I'm wrong.
The quota denial for high amount CPU and the warning message Many of
the requests to your application are taking a very long time.
Only one question, I wonder how much CPU of google is spent in
calculating high amount coutas. Pherahaps google should assign our
application that cpu time.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App
Request denials for high CPU are based on the runtime CPU usage (which
does not include the CPU used in API calls). Since the runtime CPU
cost are the ones present in the logs, it is more useful to rely on
the log information when trying to determine how best to reduce CPU
load for specific
mitnick,
Can you explain more fully what the problem was, and how you were able
to debug the problem once you knew to look at the logs vs the
dashboard? After all the back and forth on the high cpu quota issue,
I am curious about the particulars. Right now, this is how I
understand it:
In another post someone was exceeding the 5 second timeout with urlfetch
trying to get an RSS feed for a Google Docs account. I am planning on using
the Google Charts API and I wonder if I won't hit the same issue. However,
this got me thinking that writing a service like the Charting API on GAE
Anyone has any idea how this warning message is calculated? Many of
the requests to your application are taking a very long time. Please
optimize these requests.
It seems I meet quota denials every time this one shows up. I'm unable
to tune anymore if I don't know how it is calculated.
There
Hi Michael,
Thanks for putting these thoughts and that eBay best practice article
is awesome! It really helps me understand more about distribution
system. It also convinced me that global transaction is not that
important. And I have refined my code according to this article, but I
didn't
Just a couple of questions to clarify - how many indexes are there for
the Account entity and are all the fields single dimensional
properties, or are there lists in there too? And out of interest, is
it the parent of an entity group?
I would agree that a single request that involves
Thank you for digging into this issue, Michael.
There are 8 indexes on Account to support different kind of query. 3
options of order, 2 options of filter generates 6 indexes then plus 2
other ones. Only one field is list and it contains very few items and
almost never change. It's parent of
So I would like to list some of the needs that real-world business
developer expected from GAE. Why I have the right to say like this?
Because I'm a full time developer working on GAE application and
running a serious LIVE business application on GAE, and my users
already started to pay money for
On 23 syys, 12:08, mitnickcbc [EMAIL PROTECTED] wrote:
Howdy.
Because I'm a full time developer working on GAE application and
running a serious LIVE business application on GAE, and my users
already started to pay money for this service!
I understand that this is bad for your business, but
Thank you for addressing these questions. Please check my comments.
I understand that this is bad for your business, but as stated by
Google, this is a preview release off App Engine. Why would one run a
production system on it?
The thing is I didn't have resources to maintain scalable
Google should start charging for the service and let customers set
their own quotas.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to
On Sep 23, 12:15 am, gg [EMAIL PROTECTED] wrote:
Agreed. The problem at Google is very simple and has two components.
First, the engineers run the show and there is no rational voice at
Google to point out to them when they do something that does not meet
a real world demand (they make
Hopefully the initial complaint is not lost in the emotion of some of the
posts. An application which performs 200 read requests per day per user,
with 1000 users at 20-50K per read would likely get a ton of warnings and
may even be shut down. The assumption being made by Google appears to be
with
Imagine the potential consequences if any app could consume as much
resources as it sees fit at any time from that daily quota it has.
Peak load could (and would) go up unpredictably, and that would
potentially cause problems even to apps that are more optimized than
the CPU hogs. Remeber
I apologize if people don't feel good by the tone in my posts. My
whole point is to let GAE folks know that where is the pain from me
with GAE and that can help them improve GAE better. I believe I'm one
the the eagerest developers here who want to see a great success for
GAE. To see unhappy
Hi all,
Having been through a number of shared hosting situations, I'm gonna
have to say that I disagree with most of the complaints on this thread.
I think one of the main things not to lose sight of is the fact that
GAE is intended to be a scalable platform, not a generic hosting
Starred it. I agree that this is a big problem.
The quota system in general is the thorn in Google App Engine's side
and, from a public relations perspective, quite a nightmare.
Given that most people will check out an application when it's getting
a lot of publicity (and hits), the first
Starred it too. Big issue here.
- fetch an url + a put() - 2000 mcycles and more
- fetch(100) (+order, filter...) - 2000 mcycles and more
- use import.zip (level = 6 ) - 2000 mcycles and more
- GQL restriction then you need to order by python - 2000 mcycles and
more
- etc,...
This quota is
I think this is the biggest roadblock that will be preventing anyone
to develop and deploy any real world apps based on appengine.The
calculation of these warning limits is so unpredictable so how can one
be supposed to optimize the queries for these limits ?
24 matches
Mail list logo
