It's great that you guys are releasing a profiler for .Net, but I have to think there's a market opportunity for a Java profiler tightly integrated with IDEA. I'm a satisfied JProfiler user and find it's interface very nice, but it seems like there could be huge wins in directly integrating profiling into an IDE. Here's some ideas I've been kicking around that stand-alone profilers are just too cumbersome for.
1) Rather than getting performance information for the entire application run (which is rarely what you want), allow individual methods to be marked for profiling, much like the debugger allows method breakpoints now. Current profilers either don't allow this, or allow only very crude versions of it, and as a result produce far more data that is actually desirable.
2) Prebuild sets of methods to get profiling information for. For instance, show performance information and traces for just JDBC calls, or just JSP tag invocations, or just EJB lifecycle calls. Borland OptimizeIt Request Analyzer component goes down this path.
3)Allow the user turn on profiling for methods based on annotations on those methods. The user annotate individual method calls as potentially expensive, and describe the resources used (CPU, heap, database, network, etc.), and toggle acquisition and display of profiling information to just those methods.
It's great that you guys are getting into to profiler business, and I hope you don't miss the chance to build something spectacular in IDEA.