automatic_updates_modules_installed() significantly slows down module install

automatic_updates_modules_installed() should at least check the $is_syncing parameter and not show when that's TRUE, although I can't remember off the top of my head whether that gets set during site install.

It's not clear to me exactly why these need to be run immediately and can't just be shown on the status report though, or whether they couldn't be moved to a submit handler on the module install form (or even whatever page that redirects to) rather than also being done during site install, drush etc.

@tedbow and I discussed it and although we're open to other options, the thing we should do in the short term to stop the bleeding in the Starshot prototype is not run the status checks if Drupal is in the middle of being installed.

Double checked the installer and $is_syncing is explicitly set to false there, so wouldn't help by itself and we'd need the separate installer check anyway.

I think this should check both tbh - i.e. it shouldn't be doing this during a config import either, the admin has already seen the message when the module was installed on local, or at the very least won't see it during a site deployment.

I concur. I added a check for config sync, and test coverage for both scenarios.

Also tagging this as critical since it is a serious performance problem.

Looks good!

Nice idea; done. I'm restoring RTBC here on the assumption that tests will pass.

Automatically closed - issue fixed for 2 weeks with no activity.