Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 975
    • Issues 975
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • Core
  • Issues
  • #1632

Closed
Open
Opened Mar 05, 2020 by justinfreeman (Agileware)@justinfreeman🚴🏿Developer

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

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

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dev/core#1632