On Jan 5, 2008, at 11:07 PM, M. Edward (Ed) Borasky wrote:

> Instead, what you need to do is profile the Ruby script, using the
> profiling tools built in to Ruby/Rails. This is covered in a number of
> books, so I won't go into it here. The point is that you need to  
> define
> the problem, if indeed there is one, and use a *systematic*  
> approach to
> solving it.

So ruby methods won't *try* to use as much CPU as necessary, just as  
much as needed?

IE, a puts statement wont take up 100% of my CPU for a split second,  
it will only use 1%?