@AdrianLarson I finally had time to use the LimitsProfiler. I was able to take the code I wrote for Dan & I's DF16 talk and implement it into the tool - very cool. If you don't mind, this would be great to work into the post I already started writing (giving you credit of course), unless you're already working on one.

@RobertWatson Oh feel free to spread the word!

I need to add a new release that includes the objects and reports and so on.

One thing I did have problems with - not sure if it was intentional or not - I had to install the LimitsProfiler package in my org. I forked the project in github but the custom setting isn't in the repo so I wasn't able to save it to my org that way

Right, I guess you wouldn't be able to copy all the code without installing it...I've been thinking about how to reduce or eliminate that dependency

Maybe I'll move all the object dependent logic into separate classes

Why not just include the custom setting object in the github repo?

Ah hmm, I usually don't pull metadata into my repositories but that's an intriguing idea.

@RobertWatson Does it actually push into your org via metadata like that?

If the custom setting was included in the repo, I could have pushed it into my org yeah

Well as long as it was included in my package.xml

@RobertWatson Huh, cool well I'll add it then.

You can pretty safely pull most SF metadata into repositories... I'm not sure how you would be able to develop a managed package if you couldn't easily push things around

@RobertWatson I haven't developed any managed packages yet but that does make sense.

@RobertWatson Version 1.2 now includes the objects!

nice! and I like the changes to the UI

@RobertWatson Thanks! Yeah minor cleanup but it annoys me to have the button jump around, or to have to remember how many trials I've run. Automating number of trials might be a good next step (and possibly migrating to slds)