Unlike the later iterations, 7 doesn't f*ck with your access times, so the 2 second delay is definitely something on Vagrant's end.Į: to help in narrowing it down, the proposed solution of overriding these functions:Ĭ:\HashiCorp\Vagrant\embedded\gems\2.3.4\gems\vagrant-2.3.4\lib\vagrant\util\platform. With good documentation, a great collection of prebuilt configurations, and a community that willingly provides support, Vagrant is an invaluable tool for our workflow. The other commenters having even larger delays can be chalked up to the fact that Windows peaked on 7 and has been a dumpster fire of hot garbage rolling downhill ever since. Vagrant takes much of the guesswork out of creating new virtual machines for development, allowing for quick port and volume mapping, system provisioning, and replication. It looks like it sleeps for 2030ms and then does the work, and the actual work takes just milliseconds. For example, a vagrant -help takes 2031 ms to complete and vagrant global-status takes 2033ms on Windows 7 圆4. It seems that independent of the command, there is a 2 second "thinking" period before actually executing the command, which itself is fast. However this is a pretty major annoyance that the vagrant ruby script is painfully slow. Vagrant is by a wide margin the best option for running VMs on Windows, including Docker containers via boot2docker, which I find much better than the native Docker implementation. Tried this with VMWare as provider but still slow, any idea what should be modify for WMare provider? My corporate antivirus adds additional slowness so in your case it might run faster. This reduces slowness from 15 sec to 2-4 sec. Note that my provider is VirtualBox so I disabled calls to PowerShell that should return false about Hyper-V. C:/opt/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/util/platform.rb
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |