# Re: your mail **URL:** \ **Category:** Ruby\ **Created:** [October 9, 2007, 11:50pm UTC](https://www.ruby-forum.com/t/re-your-mail/116811 "2007-10-09T23:50:25Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Al\_Brown](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/58f4c7/32.png) [@Al\_Brown](https://www.ruby-forum.com/u/Al_Brown)\ **Post date:** [October 9, 2007, 11:50pm UTC](https://www.ruby-forum.com/t/re-your-mail/116811/1 "2007-10-09T23:50:25Z")
awesome. its much easier to see whats happening with the whole system imagine the same sort of thing for object interaction, method calls and db queries that showed the most commonly used and costliest, making it much easier to see what should be optimized. perhaps this already exists? ----- Original Message ---- From: Chad P. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) To: ruby-talk ML [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) Sent: Tuesday, October 9, 2007 2:22:51 PM Subject: Re: your mail On Tue, Oct 09, 2007 at 02:42:05PM +0900, John J. wrote: > Check this out. An interesting example of Ruby in use. > Data visualization. > > [http://www.fudgie.org/](http://www.fudgie.org/) > > It’s already stirred up a hornet’s nest on slashdot with plenty of > juvenile comments (some accurate) and lots nay sayers who don’t see > the potential for creativity in Ruby and data visualization > illustrated here. Holy cow, it’s too much fun to watch this program work. . . . ---
**Author:** ![Al\_Brown](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/58f4c7/32.png) [@Al\_Brown](https://www.ruby-forum.com/u/Al_Brown)\ **Post date:** [October 10, 2007, 12:30am UTC](https://www.ruby-forum.com/t/re-your-mail/116811/2 "2007-10-10T00:30:52Z")
On Oct 9, 2007, at 14:49 , Al Brown wrote: > awesome. its much easier to see whats happening with the whole system > > imagine the same sort of thing for object interaction, method calls > and db queries that showed the most commonly used and costliest, > making it much easier to see what should be optimized. perhaps > this already exists? I tried out something like this with the GC subsystem, but I ended up with poor performance because I wasn’t able to output data fast enough.