Very slow sites when running BOA from vagrant

It's not entirely clear from your post how you are mounting the directories you're sharing. But afaik vagrant uses NFS by default, and it doesn't look like there is proper mapping of your host user uid/gid to the users in the VM.

I have just set up something similar with aegir/vmware using nfs mounts, but not BOA.

Is this not proper mapping?

What was you solution for doing the mounts?

That's vagrantfile syntax,

That sounds like it could be slow network mounts, although it's unclear why this issue would then affect the site which isn't on a mounted drive.

• From http://docs.vagrantup.com/v1/docs/nfs.html

It’s a long known issue that VirtualBox shared folder performance degrades quickly as the number of files in the shared folder increases. As a project reaches 1000+ files, doing simple things like running unit tests or even just running an app server can be many orders of magnitude slower than on a native filesystem (e.g. from 5 seconds to over 5 minutes).

:nfs => true is the flag you want to add to your share_folder lines to switch from VboxFS to NFS. I'd be interested to hear your results.

_{If my comments have helped you, please pay it forward!
Use issue queues to discuss module issues - this will help your questions assist others (including yourself!) in future.}

NFS does speed things up, but causes weird permission errors in the status report. Drupal can't write to the files directory.

I tried serving directly from the VM which worked well. I even ran security review to make sure everything was setup correctly. Then copied the files to the NFS shared folder, changed the conf and restarted apache. Drupal could no longer write to the files directory.

According to this, every user should be able to write to the NFS shared folder :

https://groups.google.com/d/msg/vagrant-up/-J3UEqYXveA/icRSrqpWWGkJ

Has anyone experienced this?

@nlambert I have experienced this when using Vagrant on a mac with NFS mounting onto the host machine. In that case what I had to do was give write permissions on the host machine (Mac), then the permissions on the guest machine (VM) would take properly. It;s odd behavior, but the problem and fix are reproducible.

I've never used NFS with Vagrant. I've used the VirtualBox FS sharing. I run a windows 7 VM at home with a 20GB+ of photos in syncd folder and I haven't had issues.

Then again I don't believe the read and write is happening as fast as it would with a code base so maybe it's a real issue in this use case. If you switch back the the synced folder it might be worth install topio on the VM and see if your maxing out when hitting a page hosted on the VM.

For permissions fixes i've used the config.vm.synced_folder settings and set apache to run as the user 'vagrant' such that reading and writing wasn't an issue.

Just my $.02

I'm running Ubuntu 12.04.5 LTS as the guest OS on a Mac OS X 10.9.4. The following worked for me:
- Using NFS: http://docs-v1.vagrantup.com/v1/docs/nfs.html
- Bumping my VM RAM to 2G.
- Adding skip-name-resolve to mysql my.cnf.
- Adding/changing a innodb value in my.cnf: innodb_buffer_pool_size = 1400M (70% of guest OS RAM).

Then, I had issues writing to the Drupal files directory from the guest OS.

As a fix, I decided to run Apache on the guest OS as the user of my host OS. All steps should be run on the guest OS from the terminal.
- Stop Apache: sudo service apache2 stop
- Get the UID of the host OS as displayed on the guest OS.
- cd to the Drupal files directory and type ls -Al. On the listing, your user will be all numbers and the group will most likely be dialout (or UID of 20 which is the staff group on the host OS).
- UID of my host OS was showing on the guest OS as 662709276.
- Type sudo useradd -u YOUR_GUEST_OS_UID YOUR_HOST_OS_USER. My code looked like sudo useradd -u 662709276 rojosnow
- Edit /etc/apache2/envvars to export APACHE_RUN_USER=YOUR_HOST_OS_USER. My code looked like export APACHE_RUN_USER=rojosnow.

If Apache was running, remove the lock file since it's probably owned by www-data: sudo rmdir /run/local/apache2.

Now, restart Apache: sudo service apache2 start.

Hope it helps someone.

• omega8cc

• Arabic
• Alappuzha
• Event Platform
• Western Ohio User Group
• Goa Drupal Community
• Liverpool
• Chandigarh Drupal Geeks (C.D.G.)
• API-First Working Group
• Compony opinionated developers
• 4SPOTS