Slow RVM initialization with cygwin on a 64bit machine

I am imagining that this might get me dinged for asking such a non-specific question but I'm getting desperate at this point. I'm using cygwin (I'm a bash addict) on a Windows 7 machine with huge memory and processor speed. For some reason when I do anything with RVM I get a 30 second delay before it happens. This includes but is not limited to rvm use, cding into a directory that has RVM in it and actually cding back OUT of those directories.

When this huge delay occurs I get the most insane forking of bash in my process explorer. bash processes are forked off and then disappear rapidly during the 30 seconds. I can't figure out how to really dig into this and see what is happening.

What I'm hoping someone can help me with is开发者_运维技巧 directing me toward resources that might address this issue (yes, I've Googled a lot and haven't found what I need--and I'm still looking) or even have had experience with this themselves.

thank you in advance and please be gentle :)

---

Since windows doesn't have a native equivalent of fork, cygwin must emulate it, so it will probably be a lot slower than on a real Unix OS.

See this thread: http://cygwin.com/ml/cygwin/2008-05/msg00360.html

Also at least one person has reported that forking on cygwin 1.7 is slower than 1.5: http://cygwin.com/ml/cygwin/2010-09/msg00871.html

Does your development require Windows, or can you do your work in a VM instead?

---

Does it work in Windows? According to the FAQ, rvm is not intended to work on Windows. You should use pik to get similar behaviour in Windows (although it misses the gemsets, it allows you to switch between ruby-versions, and with pik each rubyversion has its own set of gems).