From: "M. Edward (Ed) Borasky" <znmeb@...>
Date: 2007-11-17T00:13:02+09:00
Subject: Re: rails incredibly slow (update)

Mohit Sindhwani wrote:
> Ron Jeffries wrote:
>>
>> I believe when InstantRails launches a command prompt, it does the
>> use_ruby. All that does, actually, is add ruby and mysql to the path.
>> Ruby is already there, mySql isn't ... which I would think would make
>> some things not work at all, not work slowly.
>>
>> Anyway, rails -v is 5 or 6 seconds even after use_ruby
>>
>> <sigh/>
>>   
> 
> Hmm.. I'm not sure where to look any more.  :-S
> 
> Cheers,
> Mohit.
> 11/16/2007 | 4:28 PM.

Hmmm ... maybe we should get an IRC channel up for hunting this down. 
I've got some friends who can usually nail something like this in less 
than an hour if it's a general Windows/laptop issue and not something in 
Ruby or Rails. I'm still clinging to the hope that it *is* a general 
Windows/laptop issue.

One thing you might try is CodeAnalyst from AMD. I think it works even 
on Intel processors, at least at the basic level. It will tell you if 
something is using a lot of *processor* time. If it's I/O, swapping, or 
some timeout, you won't see anything.