Considerations for Inserting Users in Bulk

User Types (Role-Based vs. High-Volume)

• Inserting role-based users (such as internal, customer, and partner users) is significantly slower than inserting high-volume community or site users.

• Test the performance of inserting users using the same type of user that will be inserted during the actual operation.

• Consider what type of users are needed for your business needs based on capabilities, security, and performance.

• When inserting role-based users, several related processes occur to make sure access is calculated correctly. These processes can result in record-level locking or group membership locking if multiple threads are inserting users. Multiple threads can occur if the user insert job itself is being processed in parallel or if there's another update job running simultaneously.

Recommendations for Inserting Role-Based Users

To expedite the processing of bulk inserting role-based users and reduce the chances of locking, we suggest that you:

• Defer group membership calculations (which also defers sharing rule calculations)

• Use sequential mode for bulk processing

• Suspend other jobs and activities that perform user, role, and group maintenance

• Use smaller batch sizes if experiencing timeouts