GitLab

End users can trigger a CiviCRM system cache flush which is an expensive process and has an overall negative impact on CiviCRM performance by just changing a Group Title or Description.

In fact, if you add, update or delete any CiviCRM Group this action will trigger a CiviCRM system cache flush and again, CiviCRM performance is impacted whilst caches are re-built.

CRM/Group/Form/Edit.php https://github.com/civicrm/civicrm-core/blob/master/CRM/Group/Form/Edit.php#L348

/**
  * Process the form when submitted.
  */
 public function postProcess() {
   CRM_Utils_System::flushCache();

CRM/Utils/System.php https://github.com/civicrm/civicrm-core/blob/master/CRM/Utils/System.php#L1450

/**
 * Reset the various system caches and some important static variables.
 */
public static function flushCache() {
  // flush out all cache entries so we can reload new data
  // a bit aggressive, but livable for now
  CRM_Utils_Cache::singleton()->flush();

Agileware Ref: CIVICRM-1443