*Thanks all guys. The problem was solved with Appstats. *
**I thougth appstats need GWT, but I just forgot to add the servlet filter
in web.xml =[ I am ashamed.
With appstats I discover too many JDO data calls being made unnecessary.
*
*
When I used the Visual VM to profile the application, it
Glad to hear it! Thanks for updating us and for further validating that
AppStats is a very important tool we should invest more into.
--
Ikai Lan
Developer Programs Engineer, Google App Engine
Blogger: http://googleappengine.blogspot.com
Reddit: http://www.reddit.com/r/appengine
Twitter:
Note that just 1174 URL Fetch calls uses 8% of my CPU.
--
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
have you ran a profiler directly in your GAE instance?
There are many factors that alter your result from a local server
On 4 February 2011 12:59, dudu eduardopich...@gmail.com wrote:
Note that just 1174 URL Fetch calls uses 8% of my CPU.
--
You received this message because you are
I can't run the profiler, because I don't use GWT on my project. I can just
use the VisualVM.
Do you think the delay to download the xml content response is responsible
for all this CPU usage?
--
You received this message because you are subscribed to the Google Groups
Google App Engine
You are doing something wrong.
Looking at my dashboard I have used 1.20 Cpu hours to fetch .5 GBytes of
data from 1464 URLs It looks like I hit my free incoming data quota long
before I hit a CPU quota.
By my calculation you would see the 1 GB data limit on a free account take
up about
But have you called the URL fetch how much times to load all this data?
My response is very short, but I need to call many times.
Maybe this is a problem in Java implementation.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to
The URLfetch quota isn't billable; you shouldn't expect that you can exhaust
most of the non-billable quotas within the free CPU you're given. You almost
certainly can't make 417 million datastore queries or serve 43 million
requests in 6.5 CPU hours either.
--
You received this message
Ok Ok Ok both are right, but I'm sorry, both are not helping me. I know that
I can't use all the quota in all fields of available resources
But, my question is:
As I posted, My task queue(see the pics) called a URL to fetch about 1000
times(see the pics). And this already cosumed 8% of my
Oh I can. Instead of use Master Slave or High Replication Datastores I use
the undocumented Zero Availability Datastore. rather than storing the data
it just returns 200 success for all queries with a null result.
There is also the option for the Full availability near zero accuracy
datastore
You're thinking of the GWT profiler. We're referring to AppStats:
http://code.google.com/appengine/docs/java/tools/appstats.html
http://code.google.com/appengine/docs/java/tools/appstats.htmlRun that to
figure out where your CPU is going. I'm going to point out that no one in
this thread can
I'll try again this appstats... i tried once but the links are not working.
I thought appstats needs GWT.
I'll post the result. Thanks.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to
12 matches
Mail list logo
