This version sports a newly retooled interface, along with numerous stability improvements and several new features. To recap, here’s some of the cool things SlimTune can do:

• Live Profiling – Why should you have to wait until your program has ended to see results? SlimTune reports results almost immediately, while your code is still running. See your bottlenecks in real-time, not after the fact.
• Remote Profiling – Other tools must be run on the same machine as the application being profiled, which can be inconvenient and worse, can interfere with the results. Remote profiling is an integral part of SlimTune.
• On-Demand Profiling – Just because your code’s running doesn’t mean you want the profiler interfering. SlimTune lets you profile exactly when and where you need it, so you can focus on the results you need instead of filtering uninteresting data.
• SQL Database Storage – Instead of developing a custom, opaque file format, we use well known SQL database formats for our results files. That means you don’t have to rely on SlimTune to be able to read your files.
• Multiple Visualizations – Most performance tools offer a single preset view of your data. Don’t like it, or want it sliced differently? Tough. With SlimTune, multiple visualizers ship out of the box to show you what you want to see, the way you want to see it.
• Plugin Support – We’re doing our best to produce the most useful visualizations, but that doesn’t mean your needs are the same as everyone else. A few dozen lines of standard SQL and C# code are all it takes to drop in your own view of the performance data, focused on what YOU want to see.

Download link and more words at the source.

Let's start with the spring of 2007 (Year 1 of the Age of XNA). As brave programmers started using XNA, they started to worry about the effects that this new form of magic would have on their surroundings, which had to be kept free of residual energies (a.k.a. garbage). People were most worried about the foreach spell, rumored to generate such energies. Thus, the mighty wizard Eli looked into the problem, and wrote two scrolls on how the foreach spell is better used, but most importantly, he left us notes on how to investigate such problems ourselves, through a ritual called memory profiling, using the CLR Profiler, and the XNA Framework Remote Performance Monitor for Xbox 360. These two scrolls can be found and read in Eli's book here and here.

At the same time, another XNA apprentice wrote about a related ritual called CPU profiling, through which other XNA apprentices could learn why their creations were slow, and lazy, by using a tool called NProf. Those that want to can still read Thomas Aylesworth's writings here.

Over a year later, bittermanandy was writing a chronicle about what recipes and rituals he found most useful in his delvings into XNA, and in one of these chronicles, he touched on the subject of the CLR Profiler again. That same year, jwatte gave away a free potion that could be used for performing the profiling ritual in the kingdom of the Xbox 360, which was not possible using NProf. MJP made a comparison between events and virtual functions, using the Stopwatch spell, and left his writing for all to read in one of his scrolls.

More recently, in Year 3 of the Age of XNA, the Grand Master Wizard Shawn, reminded all of us how important is that we use the profiling rituals as often as possible, and gave us an example of using the blunt yet powerful spell Stopwatch.

We hope you liked our return to past scrolls of wisdom, and found something of help in them. Please let us know what you think, and leave a note in the notebook below.