- Issue created by @fjgarlin
- πΊπΈUnited States phenaproxima Massachusetts
Can this wait until Drupal 11.2 is out? The reason I ask is that core changed the extension system so that a batch install like Drupal CMS's should have far fewer container rebuilds, which should result in a significant performance improvement. It won't get down to seconds or anything like that, but it might be a big enough dent that we'll want to reevaluate what to do during this wait.
- π¬π§United Kingdom catch
Agreed with #4, module install time can be reduced by 50% or more in 11.2, standard install goes from about 30-40 batch iterations down to 2. Drupal CMS has a lot more modules to install, so at least the absolute time saving should be greater, if not necessarily the percentage.
The main waiting time that's not optimized is translation download/import (although @alexpott has been working on that recently) and default content import.
Also cross-linking β¨ Add a non blocking batch runner Active . It would be theoretically possible to install the base recipe while showing the form with the optional recipe selection, with the submit button greyed out until the base recipe install is complete.
- π¬π§United Kingdom catch
π RecipeRunner::processInstall() installs modules one by one Active is also relevant here.
- π¦πΊAustralia pameeela
I'd love to do this, but there is no way we would be able to get it done before 11.2 anyway unfortunately.
I also could swear there was already an issue for this! But I can't find it.