Expected slowness of (any) vagrant command

[Marius Shekow]

Hi,

on every Windows machine I've used vagrant on, typing "vagrant <something>" will usually result in 5-7 seconds of 1 core maximum CPU use, without anything happening. This is also the case when using invalid commands, e.g. "vagrant whyyousoslowdawg" - 5 seconds of nothing happening, then the help screen shows up. On macOS it takes "only" 3 seconds.

Is this expected behavior? If yes, which specific computations are so labor-intensive? String comparisons are _MUCH_ faster, in my personal experience ;).

Cheers!

[Simon Gooch]

Hi Marius,

I would also like to get to the bottom of this. As I understand it, it's starting ruby during this time but I agree it's annoyingly slow and I would really like to speed this up.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/6f55d702-2ecc-48c8-a9e7-a4ede83a09a4%40googlegroups.com.