I guess the reason why this is so damn good is because it gives an
integrated picture across datastore, memcache and web request, without
much overhead! Given that the variations are fixed (GAE's limitation
of not allowing all libraries/api/rpc calls), this gives the full
picture of the application.

On Jan 19, 4:18 pm, mani doraisamy <mdorais...@orangescape.com> wrote:
> Thanks for the link, Danny. This is the best profiling tool i have
> used. Well done, Guido!
>
> Will get back with the performance data for off-peak Vs peak hours.
>
> thanks,
> mani
>
> On Jan 17, 9:37 pm, Danny Tuppeny <da...@tuppeny.com> wrote:
>
>
>
> > Have you identified what part of your page is taking additional time?
>
> > Guido van Rossum wrote a library called Appstats to help profile time
> > spent on API calls. I'd recommend setting it up (it works in
> > production) to see if you can identify where this time is being spent.
>
> > I wrote a short article about Appstats on my blog with some
> > screenshots showing the sort of data you can get out of it:
>
> >http://blog.dantup.com/2010/01/profiling-google-app-engine-with-appstats
>
> > Hope this helps.
>
> > Danny
>
> > On Jan 16, 8:24 pm, mani doraisamy <mdorais...@orangescape.com> wrote:
>
> > > Recently, we have been running into frequent performance problems,
> > > especially between 7-10pm IST. Requests that used to take 600ms are
> > > taking almost 4 secs.
>
> > > - Has anyone faced similar problems recently?
> > > - What is the limit for memcache per account? How do we find the cache
> > > expiry pattern? (actual expiry Vs specified expiry)
>
> > > thanks,
> > > mani
-- 
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-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.


Reply via email to