Upgrades slow as a result of snapshot code
The addition of the snapshot code causes queries to run that are slow on a large database - eg. SELECT COUNT(*) FROM civicrm_contact
- this is for a database update with NO changes to any of the large tables it is doing slow queries on.
All the messaging about the snapshot is about how to turn it ON - not about how to stop it from doing it's 'activation test'
Note the test is an arbitrary check on the size of some tables thought to possibly signal a large database - but then it turns it ALL off or ALL on after some slow queries. This means the sorts of updates we would have found this useful on (scheduled reminders) may be unnecessarily de-activated.