With my own eyes I witnessed this break lasted about a week... 
I thought you were taking a development-break? :-P
Hahaha, yes, compared to Lilly development, it's a solid reduction in efforts 
...I am just doing some "research" for possible new projects, and performance always have a key role
The script can be used already, yes. I have used it a lot.
Screenshots in this thread shows that it can be improved a lot, visually. It would be great if it could be improved and released.
I even have some ideas of how it can be improved further, for example by using graphs. With graphs showing cycle-cost over time you can more easily catch those worst-cases, and see when they coincide with other worst-cases (current version shows two numbers only: average and worst case). Ideally with a filter to toggle various "lines" (measurements) on and off.
About the tcl-remark: The best way to get anything done, is to do it yourself. So I tried, many times, to get my head around tcl. I am only able to to the simplest things. A calculation or modifying a script already made. Sometimes. But anything more, like something containing visuals, openmsx-values, whatever, is still really alien to me. I can read and write C, C++, Java, python, perl, bash, SQL, z80 assembly and some Javascript. But tcl - for some reason it is not for me, I gather 
So, I would be dependent on others. Maybe someone else could improve this awesome tool
