RavenDB Profiling Support
When we built the RavenDB profiling support, we intentionally built it in such a way that you can have multiple ways of accessing it.
Out of the box, we come with a VS debugger visualizer and an MVC Profiler for your websites. The VS Debugger Visualizer is pretty ugly (fully functional, of course, just not that pretty), but we are very proud of the MVC Profiler support and how it looks:
The real fun part is that we aren’t the only ones that can access those API, the screen shot below was taken from a Glimpse extension that adds RavenDB Profiling support:
That is quite impressive, even if I say so myself, and it shows what happen when you aren’t overly fond of the internal keyword.
Comments
The glimpse plugin will have a full repo up at github soon. I am just improving the rendering of result documents and a couple of other minor things. It's very cool.
"Out of the box, we come with a VS debugger visualizer and an MVC Profiler"
Any documentation about how we can use this/these?
i know how to use VS deb vis's .. but not mvc profiler .. and maybe some other people might not know, also?
@Justin You need to get an unstable build that includes the Raven.Client.MvcIntegration.dll
http://builds.hibernatingrhinos.com/builds/ravendb-unstable Build 402 and up will.
Add a reference to the dll to your project.
Then where you create your DocumentStore instance (usually global.asax unless you are doing something with IoC or bootstrappers) you need to pass that instance to the profiler. Raven.Client.MvcIntegration.RavenProfiler.InitializeFor(myDocumentStore);
Finally in your Layout/Master page, in the head section add this line @Raven.Client.MvcIntegration.RavenProfiler.CurrentRequestSessions()
It will inject the script code needed to hook everything up and load any other dependencies that are not present (such as jQuery).
http://github.com/csainty/Glimpse.RavenDb
http://nuget.org/List/Packages/Glimpse.RavenDb
Still very much in beta, let me know what you think. It doesn't use the Raven.Client.MvcIntegration.dll, just talks straight to the profiling API, so it is functional on the current stable release sans timing information that is only in unstable builds at the moment.