This post originated from an RSS feed registered with Ruby Buzz
by Huw Collingbourne.
Original Post: Ruby Debugger Timings
Feed Title: Ruby In Steel
Feed URL: http://www.sapphiresteel.com/spip.php?page=backend
Feed Description: Developers' Blog of the Ruby In Steel and Amethyst (Adobe Flex) IDEs for Visual Studio
Here are the results of some simple benchmarks comparing the three Ruby debuggers - the original slow Ruby debugger, ruby-debug and Cylon. As I mentioned last week there are two main types of benchmark tracing that Ruby provides. One traces a ‘line' execution and the other traces a ‘call' invocation. For ‘line' based code (such as i = i + 1), the tracing overhead is the same for all lines. For the other ‘call' trace, the overhead varies a bit (...)
Previous Topic
