I have been using Appstats to optimize my applications as needed. It is great for finding the chain of gets and zero in on problems. The current version helps me to zero in on urls that use a lot of RPC's. This is not as interesting with the new pricing scheme where I am starting to spend more time thinking about reducing latency (to reduce frontend instance hours) and datastore reads.
It would be a lot more helpful if Path Stats was sortable by "real" time rather than #RPCs. It looks like you already have all of this data, someone just needs to add the column in the GUI besides the #RPCs column and let me click to sort by "real". Then I can more efficiently prioritize url optimization by latency. Chris On Sep 7, 11:59 am, "Gregory D'alesandre" <[email protected]> wrote: > Its a good idea, we'll see what we might be able to do about it. > > Thanks, > > Greg > > On Thu, Sep 1, 2011 at 11:06 PM, _vjy <[email protected]>wrote: > > > > > > > > > It would be really great if appstats could include billing details. This > > way a developer > > would know exact billing amount, in development server environment. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine" group. > > To view this discussion on the web visit > >https://groups.google.com/d/msg/google-appengine/-/xhGfnvdnPpgJ. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > >http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
