-
Notifications
You must be signed in to change notification settings - Fork 846
More memory #427
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I had problems with memory running over as well. I fixed it by dropping in a config.vm.provider :virtualbox do |v|
v.customize ["modifyvm", :id, "--memory", 1024]
end |
I had not realised you could override parameters like that. 😄 |
Is this worth bumping the memory limit by default? |
|
Agreed. 512 is pretty low, given this is aimed at "a common configuration for working with high traffic WordPress sites". |
I've upped mine to 2048.. I wouldn't mind a higher default. Luke Woodward – Senior Strategic Engineer On Tue, Aug 26, 2014 at 9:57 AM, Daniel Bachhuber notifications@github.com
|
1GB seems to be a nicer answer than 512MB by default. A Customfile can be used to reduce or raise the memory footprint to another level. Fixes #427
One small interjection: On Thu, Sep 4, 2014 at 12:14 PM, Jeremy Felt notifications@github.com
-Doug |
Maybe the docs should reflect this and advise a customfile for such users? This is a good idea. We can find a way to link to https://github.com/Varying-Vagrant-Vagrants/VVV/wiki/Customising-your-Vagrant's-attributes-and-parameters in the README. I'd also like to find a way to make a few of these things customizable through a config (YAML) file of sorts that can be excluded from git. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Is anyone else running into issues with the VM not having enough memory? I'm seeing this with Composer:
See: composer/composer#945 (comment)
The text was updated successfully, but these errors were encountered: