Promit's Ventspace

November 3, 2009

SlimTune Plans

Filed under: SlimTune — Promit @ 10:27 pm
Tags: , , ,

I had to sit down and figure out exactly what to do about SlimTune. People really, really like that little thing, which is amazing for something I put together in six weeks. It doesn’t deserve to die, so I’m going to make sure it doesn’t. That said, it looks like it will be a while before I get back to it. January, to be exact. Unfortunately, I need to buckle down and finish my degree right now, and I can’t really afford to commit to a side project.

That’s the bad news. The good news is that I haven’t stopped thinking about the project, and I’ve figured out how to do some really sweet stuff. Let’s recap. The current release of SlimTune is a purely sampling based profiler. The goal is to enable instrumentation and hybrid modes for public use. They actually already work, except the data is thrown away by the frontend. I’ve been unsure of how to collect it in a useful way, but I’ve got some ideas now that will give you some serious detail. Min/average/max will be there, but who cares? I can give you a graph with timings, showing you the actual characteristics of the function. So if it often takes 5ms or 50ms, but nowhere in between, you’ll see two spikes at 5 and 50. The average might be 30ms, but that’s basically a bogus number in these situations.

I’ve also got some UI improvements scheduled. Probably chief among them is to fully enable custom visualizer plugins, so you can throw together your own views of the data. I’d really like to enable some kind of graphing support, but we’ll have to see how that goes. It’s tricky to find a chart control that also has favorable distribution terms. I was using MS’ chart control for the teaser photos, but it really sucks — or at the very least, I don’t understand how to use it the way I want to. Things get sized very strangely, for example. I’ll figure something out.

Oh, and people are practically begging for a way to save and load launch configurations. I promise you, that’s top of the list. It annoys me too. I did it in six weeks, remember? It will be fixed.

Now, here is the important bit. For those of you who are interested in SlimTune, I have a request! File issues against the profiler for anything you want. And I don’t just mean bugs. UI and other feature requests are welcome! You can even request things I’ve promised I will do. That’s totally fine. Hit me with everything you’ve got people! That way I know what’s most important to YOU, not me.

5 Comments »

  1. […] Roy talks about the future plans of SlimTune and asks to file issues and feature requests against it (without actually providing a link, though, […]

    Pingback by A Slim Future and Fat Past « Sgt. Conker — November 6, 2009 @ 7:21 am | Reply

  2. Noooo

    I just found this. My app (IronScheme) breaks all profilers, so it is nice to see something opensource I can tinker on. I have built a log only compiler for IronScheme that works. Anything else would be a bonus 🙂

    Cheers

    leppie

    Comment by leppie — November 11, 2009 @ 10:30 am | Reply

  3. Awesome!

    It works 100% with IronScheme! 🙂

    Good job, thanks.

    Comment by leppie — November 11, 2009 @ 10:36 am | Reply

  4. For the graph library, I quite like zedgraph(http://zedgraph.org/).

    SlimTune comments:

    A way to collect data without having to save anything(although if the run dialog remembers a file which is overwritten that would be nearly as good) would be nice.

    Plus some way to turn profiling on/off from the app or a time delay so that I can wait for my app to finish initialization (+ a length for the profile). At present switching away from the app and using the clear button works, but pollutes the profile somewhat.

    Profile on/off buttons are important as well if profiling modes slow down the app by a huge amout(presently more or less OK). Similar to CLRProfiler. Otherwise initialization can take a very long time.

    Comment by David Black — November 18, 2009 @ 9:12 am | Reply

    • Collecting data without saving a file is a no-go at the moment because there’s only one storage engine backend and it does not support in-memory databases. One option would be to to add another engine which does, but what I might actually do is generate a temporary file if the save location is left empty. The new run dialog does remember your file selection though.

      Profiling on/off as far as data collection is essentially good to go minus UI, and you should get it for the next version. Right now profiling is on whenever a profiler is connected, so I need to work on a smooth connect/disconnect mechanism that isn’t confused with start/stop of data collection. I need to figure out exactly what options to show and how to describe them, basically.

      Comment by Promit — November 18, 2009 @ 9:23 am | Reply


RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Create a free website or blog at WordPress.com.

%d bloggers like this: