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
Update to Trusty Tahr 14.04 LTS #334
Comments
Is there a reason we can't go to 64 bit during this move? I've been playing some with HHVM, and it's pretty simple to adjust my VVV to use it except that it needs a 64bit box. I switched to precise64 a while ago and everything has been great. |
+1 On 64bit VM. It's pretty standard now. |
Last I heard (it was a few years ago) most web servers were sticking with 32bit because it was just as fast and wasted far less memory. That certainly could have changed in the last few years, but I wouldn't assume going to 64bit offers any benefit and may have some negatives. |
One very large benefit: the potential to use HHVM. There IS no 32bit port of HHVM; it requires 64bit OSes. Doug Stewart
|
I think we should definitely try 64. I've been running 64bit CentOS in another setup just fine for a while now. We used precise64 at the beginning — b4465c6 — and then I have this great commit message explaining the shift to precise32 in 113e359: Try the 32bit version of 12.04 for a while and see what happens. Also bump the machine up to 512MB from the default of 360MB. So there's that. :) Similar to what @jb510 points out, the decision could have been made based on the memory used by the VM and some perception of slow down at the time. |
Most of the servers I work with are 64bit. Having said that, most servers I work with run 8+G of ram, so it only makes sense. In my, admittedly slanted, experience, more and more places are moving to 64bit OSs. You no longer have the instability issues you once had with 32bit programs acting flaky on 64bit systems, because everyone writes for both now (except the few super-progressives like HHVM, who only write for 64bit). Everything in VVV should run perfectly on Trusty64, and it would be less limiting for people using it to experiment with things like HHVM (which I'm doing, and I know others are as well). |
This has bad impact on people who have intel processor which doesn't support Virtulization Technology. |
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. |
Trusty Tahr 14.04 LTS is officially out...
Offical Vagrant VB box builds here:
https://vagrantcloud.com/ubuntu
I think this is the URL to use (at least I'm using it for testing)
https://vagrantcloud.com/ubuntu/trusty32/version/1/provider/virtualbox.box
The text was updated successfully, but these errors were encountered: