What is next for the profilers?
We have been working on the profilers (NHibernate Profiler, Entity Framework Profiler, Linq to SQL Profiler, LLBLGen Profiler and Hibernate Profiler) for close to three years now. And we have been running always as 1.x, so we didn’t have a major release (although we have continual releases, we currently have close to 900 drops of the 1.x version).
The question now becomes, what is going to happen in the next version of the profiler?
- Production Profiling, the ability to setup your application so that you can connect to your production application and see what is going on right now.
- Error Analysis, the ability to provide you with additional insight and common solution to recurring problems.
- Global Query Analysis, the ability to take all of your queries, look at their query plans and show your potential issues.
Those are the big ones, we have a few others, and a surprise in store
What would you want to see in the next version of the profiler?
Comments
For me, production profiling is easily the killer feature that we've been waiting for.
Better support for remote profiling would be great too..especially if it could be done via. a hosted silverlight application, eliminating the need to have the profiler installed locally and to send all of the profiling information over the wire (not sure about the feasibility of that, though).
You've already implemented the few really minor thing's I've emailed you.
But something around remote debugging would be great, but locked down to a specific IP or something. So I can only see querying done for the requests I'm making, and it doesn't capture anything else.
I think the interface for showing query plans needs an overhaul, I still use SQL Server Management Studio for looking at query plans because it just feels too clunky in NHProf.
Also something to exclude sessions from certain URL's, for some web pages with AJAX requests I end up with a few sessions when all I want to profile is the initial page load or a single AJAX request.
Otherwise, I've gone from hating NHProf because it was expensive program that didn't justify it's cost (in my opinion) when initially released. To a bloody useful program that I now use on a daily basis. :)
NC, Regarding the ability to exclude sessions, have you checked out the Filter feature?
As always - validation of the mapping and configuration and suggestions regarding how they could be optimised.
Clearly you're one step ahead of me, feature works perfectly, I had fiddled with it a long time ago in the trial but didn't take much notice. But it does exactly what I need it to do, and more!
What would be nice is to be able to connect the profiler to multiple running applications.
This would allow analysis of front and back-end apps in one go (web -> different connected services, like servicebus hosts).
Better 2nd-level cache analysis and optimisations (e.g. what causes evicts)
RavenDB profiler maybe?
Any chance of ruby ActiveRecord profiling. I really do miss NHib prof since i left the world of .net
Colin, Active Record? As in Ruby? Or as in Castle Active Record?
I'd like you to revisit the idea of an actual uber-prof. It'd be nice to have a profiler that would work with any ORM technology
What I would love to see is a generic DB connection handler to support all the Micro-ORM's out there. I know that it won't be as un-obtrusive as the current profiler support, but it would be great new product line that I would buy.
What about events stream profiling? Kind of CQRS Profiler or so
Production profiling would be wonderful!
Production profiling would be fabulous however I would like to chirp in and say this must work in medium trust scenarios.
Just my two cents
Ayende, I think Colin meant Ruby, as he also said he's left the .NET world.
Joe, I think if you need a RavenDB profiler, you're doing something seriously wrong.
@Simon That's why I would want it :-D
Production profiling! And perhaps a tad of error analysis aswell..
Raw sql profiler for all legacy code that uses less popular ORMs or no ORM at all.
Rafal, Have you checked out our CustomReporting option?
Jamie, * You might want to look at NHibernate Query Analyzer. What you request is something that we aren't likely to support inside the profiler. * I would like to see what you mean by improving insert layout. * As for the last one, we aren't likely to support it, it requires a LOT of information about the actual DB engine, and at that level, you are probably better off using the database own mechanisms, rather than a higher level tool like the profiler
Error Analysis and Global Query Analysis would really make me buy nhprof.
Comment preview