Named Volume Performance Feature

[dustinleblanc]

As a Mac OS / Windows Lando user,
I want to selectively mount paths within my application in named volumes,
So that I can increase my development speed by bypassing a significant portion of the speed penalty imposed by Docker's underlying filesharing mechanisms.

Notes from today's discussion:

• Feature should be activated in each app specifically, within it's .lando.yml
• 'Easy button' inside recipe config that would activate for common paths (D8 - vendor, core, etc).
• Exclude key in root of lando.yml takes an array of paths that are relative to app root
• On rebuild we spin up a util container, that copies the exclude paths into their respective volumes, then stops, starts the app, and mounts those volumes in the needed locations.
• Upon disabling of feature, don't do anything with mounted code, notify user of change, and give them steps to remediate.
• start/stop/restart should make no changes, rebuild required for all ops
• potential future feature is two-way syncing, or even, container-authorative one way syncing.

[pirog]

@dustinleblanc so have some initial stuff over in https://github.com/lando/lando/tree/hyperdrive-motivator

the syntax is as follows

name: my-lando-app
excludes:
  - vendor
  - modules/contrib

And requires a lando rebuild.

We also could consider adding support for this sort of syntax as well, eg exclude all of X except Y, but that might be better as a separate issue.

name: my-lando-app
excludes:
  - modules/contrib
  - '!modules/contrib/search_api'

[pirog]

@dustinleblanc dropping a note here:

1. Let's make sure we create any exclude directories that don't exist

[pirog]

@serundeputy... adding you to the party here. Dustin and I need a third opinion, can you...

1. Get lando running on macOS from source with https://github.com/lando/lando/tree/hyperdrive-motivator checked out
2. Get the dgreat and pe sites spin up with database and files and all needed things pulled
3. Try out a few time lando drush cr and time lando drush status and log the average times somewhere

Then let's meet and see if we can get the hyperdrive-motivator working. Here are my stats for dgreat

without excluding

lando drush status: 20s
lando drush cr: 1m30s

excluding vendor, web/core and web/*/contrib

lando drush status: 1.3s
lando drush cr: 19s

So one thing i did notice @dustinleblanc (and @serundeputy), was restarting docker seemed to be necessary to get these gains to show up. No idea why but until i did that i saw "good" performance improvements but not "great"(eg the above) ones

[serundeputy]

In order to get the performance increase I had to restart docker as @pirog also indicated.

dgreat

sans exclude

lando drush st
  real	1m56.403s
  user	0m0.907s
  sys	0m0.287s

lando drush cr:
  real	2m39.110s
  user	0m0.816s
  sys	0m0.280s

excluding vendor, web/core, and web/*/contrib

lando drush st:
  real	0m3.855s
  user	0m0.657s
  sys	0m0.318s

lando drush cr:
  real	0m15.643s
  user	0m0.724s
  sys	0m0.175s

pe

sans exclude

lando drush st: 
  real 0m1.328s
  user 0m0.457s
  sys 0m0.507s

lando drush cc all:
  real 3m0.532s
  user 0m0.808s
  sys 0m0.183s

excluding vendor, sites/all/modules/contrib

lando drush st: 
  real	0m3.120s
  user	0m0.628s
  sys	0m0.163s

lando drush cc all:
  real	1m16.717s
  user	0m0.699s
  sys	0m0.313s