many development enviroments would do good with some graphics representation of how much of the plattforms capabilitys is actually used up during a test run, ho

many development enviroments would do good with some graphics representation of how much of the plattforms capabilitys is actually used up during a test run, how cache friendly the code is, and how much your latest changes affected this. And this coloured columns need to show in every svn/git commit message. Profiling needs to be not something that the embeded guy does after you messed it up. Jerry Commited: +25% more time spend in function xy, due to chace unfriendlyness.. If you see it, and your colleagues see it, it becomes a issue. If it becomes a issue the perpetrator will look into it.