Slow ACL observer in system logsIssue In system logs observed messages like: Slow ACL 0bcff9740a0006d400ae1a384168533a for the path record/sys_attachment/create , time was: you 7ReleaseAllCause- Slow ACL log - It is the time that is not impactful on instance accessibility by users , integration services, etc.It is a diagnostic value, and it will vary depending on table sizes and type of ACL implementation (e.g. roles only vs scripted)Its sole purpose is to help detect ACLs that create performance bottlenecks.- 5ms threshold value is historic, and detects outliers from average on a OOB instance with some sample load. If you have large tables, many ACLs might appear as "slow" per 5ms threshold.However, "visual" performance degradation is usually evident when ACL execution times are in seconds.- you can increase thresholds to diminish syslog clutter to reasonably high values in milliseconds range to recommended 50ms by creating the system property "glide.security.slow_acl_threshold" and "glide.security.slow_df_threshold".ResolutionTo reduce the volume of logs, you can add/override the following properties, determining the threshold time for an ACL/Secuirty Attributes to be considered slow. The properties do not exist by default. Steps to proceed:- go to sys_properties table and create a new sys property with the:- name: "glide.security.slow_acl_threshold"- type: "string" or "integer"- value (in ms) - your choice- save- repeat for "glide.security.slow_df_threshold"- run cache.do