Designing Record Access for Enterprise Scale

Designing Record Access for Enterprise Scale
Preface
Introduction
Group Membership Operations and Sharing Recalculation
Common Group and Data Updates
Ownership Data Skew
Group Membership Locking
Takeaway: Tuning Group Membership for Performance
Object Relationships, Bulk Loading, and Sharing Recalculation
Tools for Large-Scale Realignments
Conclusion
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Takeaway: Tuning Group Membership for Performance

Understand the performance characteristics of the various group maintenance operations that you are performing and always test substantial configuration changes in a sandbox environment so you know what to expect in production.

Here are some specific suggestions.
  • Identify user and group updates that are complex, such as user role and portal account ownership changes, or updates that involve a large amount of associated data. Allow for additional time to process these changes.
  • When making changes to the hierarchy, process changes to the bottom (leaf) nodes first, then move upward to avoid duplicate processing.
  • Limit the number of records of an object owned by a single user to 10,000.
  • Tune your updates for maximum throughput by experimenting with batch sizes and using the bulk API, where possible.
  • Remove redundant paths of access, such as sharing rules that provide access to people who already have it through the hierarchy.
  • Schedule large group membership operations during off-peak hours.