This repository has been archived by the owner on Nov 24, 2022. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
My case is a bit unusual - we have near 200 machines defined by single Vagrantfile.
I found that command 'vagrant status' takes near 82seconds to run on empty setup. With strace I see that there are a lot of open("...vagrant-lxc-1.2.1/locales/en.yml") requests.
With attached patch time of 'vagrant status' reduced to 32seconds.
Configuration:
Ubuntu 16.04.1
Vagrant Version: 1.8.5
vagrant plugin list:
vagrant-lxc (1.2.1)
vagrant-share (1.1.5, system)