There's nothing for that out-of-the-box. You have several options. An easy one is to stash a list of (url, max-time) pairs in memcache.
A slightly harder one is to customize appstats.
There's nothing for that out-of-the-box. You have several options. An easy one is to stash a list of (url, max-time) pairs in memcache.
A slightly harder one is to customize appstats. The rub is that a handler can run long for several reasons that aren't under your direct control (e.g. , a request that causes a new instance to be spun up is going to take longer), so knowing what the longest one is might be of little help if the longest was a fluke.
You can work on a good Yslow score. If you make your webpages so that they get a good score in Yslow then I think you have a good case. You can also take the usual measures for optimization i.e.
Memcache, instance variables, javascript, more efficient data structures and such. Specifically if you get a score such as 70 % in yslow then it's probably alright.
Go to the Google App Engine dashboard and click on Logs in the left panel. Then select the All Requests radio button and expand the options box. Then type in ( ms=)(0-9{5,}|5-90-9{3}) in the regex box.
This will return all logs where ms=5000+ milliseconds. You can then tune the regex expression to return then number of logs you are interested in.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.