Running stuff in /vagrant is slow (and NFS could make it faster)

[adamtheturtle]

Replaced by https://clusterhq.atlassian.net/browse/FLOC-516

We recommend at http://docs.clusterhq.com/en/latest/gettinginvolved/contributing.html that people use Vagrant and tox.

Running tox -e sphinx took over 5 minutes on my Vagrant box, even with many requirements "already satisfied":

real    5m3.064s
user    0m14.197s
sys 1m8.590s

Running tox -e sphinx was reasonable without Vagrant:
first time:

real    0m45.671s
user    0m29.185s
sys 0m9.195s

second time, with requirements "already satisfied":

real    0m9.530s
user    0m5.914s
sys 0m1.722s

I think that our recommendations aren't suitable for development.

My config: OS X Mavericks, mid-range Macbook Air

[adamtheturtle]

python setup.py --version as required by the release process takes a long time too. 2 seconds on my Mac, 1.5 minutes on Vagrant.

[adamtheturtle]

EDIT: The below is incorrect

It could be something to do with:

if os.path.abspath(__file__).split(os.path.sep)[1] == 'vagrant':
    del os.link

in setup.py

[adamtheturtle]

I have fixed this on my machine by using NFS, to get over some of the virtual box shared folder performance issues. tox -e sphinx now runs at approximately 10x speed, but still 3x slower than outside Vagrant.

http://docs.vagrantup.com/v2/synced-folders/nfs.html

real    0m34.151s
user    0m5.973s
sys 0m5.938s

[adamtheturtle]

We are moving our development planning to JIRA. This issue is now being tracked at https://clusterhq.atlassian.net/browse/FLOC-516. You are welcome to file additional issues in GitHub if that's easier for you.