Difference between revisions of "Admin Console Performance Issues when using Delegated Admin"

(short_term_all_effective_rights_cache_expiration)
Line 17: Line 17:
  
 
=== short_term_all_effective_rights_cache_expiration ===
 
=== short_term_all_effective_rights_cache_expiration ===
  <attr id="1903" name="zimbraShortTermAllEffectiveRightsCacheExpiration" type="duration" cardinality="single"  optionalIn="globalConfig,server,alwaysOnCluster" flags="serverInherited,serverPreferAlwaysOn" affectsServices="all"  since="8.7.0,9.0.0">
 
    <globalConfigValue>50s</globalConfigValue>
 
    <desc>Maximum time an entry in the short term All Effective Rights cache will be regarded as valid.
 
    If value is 0, the cache is disabled.
 
    The cache is particularly useful when significant use is made of delegated administration.
 
    This cache can improve performance by avoiding recomputing All Effective Rights of named entries like accounts  frequently in a short period of time.
 
    All Effective Rights are computations of the rights that named entries like accounts have - although when used, they  are checked separately.
 
    The longer the value of this setting is, the more stale the view of the details is likely to be.  For this reason,  the maximum accepted value is 30m.
 
    Larger values will be treated as being 30m
 
    </desc>
 
  </attr>
 
  
 +
Maximum time an entry in the short term All Effective Rights cache will be regarded as valid.
 +
If value is 0, the cache is disabled.
 +
The cache is particularly useful when significant use is made of delegated administration.
 +
This cache can improve performance by avoiding recomputing All Effective Rights of named entries
 +
like accounts frequently in a short period of time.
 +
All Effective Rights are computations of the rights that named entries like accounts have - although when used, they are checked separately.
 +
 +
The longer the value of this setting is, the more stale the view of the details is likely to be.
 +
For this reason, the maximum accepted value is 30m.
 +
Larger values will be treated as being 30m
 +
 +
The default value is '''50s'''
 +
 +
This will be replaced in 8.7 and 9.0 with the LDAP attribute:
 +
'''zimbraShortTermAllEffectiveRightsCacheExpiration'''
  
 
=== short_term_all_effective_rights_cache_size ===
 
=== short_term_all_effective_rights_cache_size ===

Revision as of 10:09, 5 May 2015


Note: This information is related to Bug 97743.

Overview

If you are experiencing significant admin console performance issues when using delegated admin, configure the following LC keys to resolve the issue:

  • short_term_all_effective_rights_cache_expiration (default: 50000)
  • short_term_all_effective_rights_cache_size (default: 128)
  • short_term_grantee_cache_expiration (default: 50000)
  • short_term_grantee_cache_size (default: 128)

Note: The default sizes are 128, with default expirations in milliseconds. Using higher values is not recommended. These keys will be moved to LDAP for 8.7 and 9.0.


LC Key Descriptions:

short_term_all_effective_rights_cache_expiration

Maximum time an entry in the short term All Effective Rights cache will be regarded as valid. If value is 0, the cache is disabled. The cache is particularly useful when significant use is made of delegated administration. This cache can improve performance by avoiding recomputing All Effective Rights of named entries like accounts frequently in a short period of time. All Effective Rights are computations of the rights that named entries like accounts have - although when used, they are checked separately.

The longer the value of this setting is, the more stale the view of the details is likely to be. For this reason, the maximum accepted value is 30m. Larger values will be treated as being 30m

The default value is 50s

This will be replaced in 8.7 and 9.0 with the LDAP attribute: zimbraShortTermAllEffectiveRightsCacheExpiration

short_term_all_effective_rights_cache_size

 <attr id="1902" name="zimbraShortTermAllEffectiveRightsCacheSize" type="integer" min="0" cardinality="single"   optionalIn="globalConfig,server,alwaysOnCluster" flags="serverInherited,serverPreferAlwaysOn" affectsServices="all"   since="8.7.0,9.0.0">
   <globalConfigValue>128</globalConfigValue>
   <desc>Maximum number of entries in the short term All Effective Rights cache.
   This cache can improve performance by avoiding recomputing All Effective Rights of named entries like accounts   frequently in a short period of time.
   Can disable the cache be specifying a value of 0
   </desc>
 </attr>


short_term_grantee_cache_expiration

 <attr id="1901" name="zimbraShortTermGranteeCacheExpiration" type="duration" cardinality="single"   optionalIn="globalConfig,server,alwaysOnCluster" flags="serverInherited,serverPreferAlwaysOn" affectsServices="all"   since="8.7.0,9.0.0">
   <globalConfigValue>50s</globalConfigValue>
   <desc>Maximum time an entry in the Grantee cache will be regarded as valid.
   If value is 0, the cache is disabled.
   This cache can improve performance by avoiding recomputing details frequently in a short period of time, for instance   for each entry in search results.
   The cache is particularly useful when significant use is made of delegated administration.
   Grantees objects provide a view of what rights a grantee has - although those are checked separately.
   The longer the value of this setting is, the more stale the view of the details is likely to be.  For this reason,   the maximum accepted value is 30m.
   Larger values will be treated as being 30m
   </desc>
 </attr>


short_term_grantee_cache_size

 <attr id="1900" name="zimbraShortTermGranteeCacheSize" type="integer" min="0" cardinality="single"   optionalIn="globalConfig,server,alwaysOnCluster" flags="serverInherited,serverPreferAlwaysOn" affectsServices="all"   since="8.7.0,9.0.0">
   <globalConfigValue>128</globalConfigValue>
   <desc>Maximum number of entries in the short term Grantee cache.
   This cache can improve performance by avoiding recomputing details frequently in a short period of time, for instance   for each entry in search results.
   Can disable the cache be specifying a value of 0
   </desc>
 </attr>
Jump to: navigation, search