Figure out recommendations for Drupal 8 deployment challenges

Had a long discussion with Moshe and Alex today about unique deployment challenges in D8, thanks to compiled PHP, which will only be exacerbated when Twig lands in full.

Here are some details I remember... this will probably need a better issue summary:

- Drupal does certain required bootstrap functions (e.g. service registration) as Symfony "compile passes." This effectively makes the PHP compiled service container hit on every page load. With Twig that's only going to become more true.
- On multi-head environments, using the default configuration that core gives you, this compiled PHP directory will end up on an NFS mount or similar. These are not at all particularly fast, which is going to lead to major performance problems.
- While the Drupal-tuned hosting companies (think Acquia, Pantheon, etc.) will probably invent workarounds for this with their various Very Smart People™, and high-end Drupal sites (think Examiner, Whitehouse, etc.) might be able to do workarounds like turning off the modules page on their servers so that the service container doesn't ever need to be recomplied, it leaves Drupal SaaS providers, as well as users of generic multi-tier hosting platforms (think Rackspace Cloud) in a pretty bad place.

One workaround that Alex suggested was disabling APC's filestat option which would improve performance on NFS, but that is unfriendly to other non-Drupal applications that might also be run on the same box. It might also mean a restart of Apache to deploy which seems like a deal-killer. :\

Since high-traffic sites are a significant portion of Drupal's target audience, this is a pretty big issue. In what ways can we mitigate these challenges prior to release?