I'm most interested on what kind of use this is getting -- @alvins, are you using it on production? If so, do you have any measurements on the performance penalty of running the profiler with a particular config (e.g., with all public methods profiled)?
And/or: a general roadmap and summary of status/stability...
I've gained large amounts of benefit out of it in development of my startup Pocketbook (https://getpocketbook.com). Because of it's 'live on-page' nature you can quite quickly see 'intensive' areas that you need to look at.
I would class it as beta and have been using/iterating it for over 4 months. However - the initial code-base was seeded from gae-mini-profiler which already had some mileage. I've added the annotation and sql profiling and made it non-gae based so we can all use it.
I don't have any roadmap as yet - if people want specific features out of it - happy to help.
I suspect the main additions you'll need for this to be useful in a production environment will be around logging and accessing stats -- showing the end user that a particular page performed poorly doesn't help you unless you also know about it, with enough info to reproduce the problem. Also, with higher volumes, you don't want to be flooded with almost-identical data, so you can dig into strategies like only sampling a subset of actual requests, different handling for poorly-performing queries, etc..
I'll keep an eye on this, and if we do decide to integrate it I'll be in touch; thanks!
