During , data packets are loaded in to memory to process synchronization objects in parallel. The size of these data packets can be increased to speed up synchronization but this required more memory. By default, the size of the data packet is selected such that the ratio of memory to performance is balanced out. However, memory issues can still occur during synchronization. This often depends on the configuration of the system environment, the amount of data to synchronize and the exact synchronization configuration. You can control memory usage to avoid such problems. The degree of change is determined with the performance/memory factor.
The performance/memory factor can be set for each separately because the amount of data varies from object to object. The first thing to do if a memory problem occurs during synchronization, is to find the affected synchronization step. Reduce the performance/memory factor for this synchronization step until you find the optimal balance between memory requirements and performance.
To adjust the performance/memory factor for a synchronization step
- Edit the synchronization step properties.
For more information, see How to edit synchronization steps.
- Select the Extended tab.
- Use the slider to set the performance/memory factor.
- Move the slider to the left to reduce memory usage. This reduces performance.
- OR -
- To increase performance, move the slider to the right. This requires more memory.
- Click OK.
The performance/memory factor specifies the percentage with which the reload threshold, partition size, and bulk level are applied to an object type.
Related topics
To improve performance when loading a , you can save the synchronization project’s configuration data as a shadow copy in the One Identity Manager database. After that, the synchronization project is only loaded from the shadow copy. The project loads noticeably faster. The shadow copy is saved in the Configuration data column (DPRShell.ShadowCopy).
If you want to use this option, take note of the following:
-
The shadow copy does not contain any changes that were made directly in the database and not in the .
-
If the One Identity Manager database is encrypted or decrypted with the Crypto Configuration program, the shadow copy is deleted.
-
If changes to the synchronization project in another database are exported, the shadow copy is deleted in the other database. This ensures that the shadow copy does not contain outdated configuration data.
Prerequisite: The transport package was created with the Transport of synchronization projects export criteria.
-
If the Enable shadow copy option is set, the daily tasks check whether a shadow copy is saved or not. If the shadow copy is missing, it is created.
To enable the shadow copy
-
Edit the synchronization project’s properties.
- Select General on the start page.
- Click Edit.
- On the General tab, set the Enable shadow copy option.
- (Optional) If the shadow copy on needs to create if the synchronization project is active, set the Only if the synchronization project is active option.
- Click OK.
Related topics
Use the to configure connections for different target system in One Identity Manager. The components of a synchronization configuration are used for both synchronization and for provisioning and synchronizing single objects. Synchronization can be configured so it can be used for connecting different target systems of the same target system type.
There are different ways to start the .
- From the Windows start menu using the entry One Identity | One Identity Manager | Configuration | Synchronization Editor.
- From the Launchpad.
- In the Manager
