Synchronization of large number of objects on large deployments may take more significant amount of time The following table shows approximate expected timing of importing and exporting synchronizations in a P6 - P6 large environment.
Note: The real synchronization time may vary and time depends on many performance factors. Refer to the Deployment Considerations of this document.
Scenario 1: Importing Resources in Large Deployments | |
---|---|
Objects in Synchronization | Units |
Number of RESOURCEs | 10,000 |
RESOURCE CODEs for each RESOURCE | 5 |
Number of UDFs for each RESOURCE | 5 |
RESOURCE ASSIGNMENT for each RESOURCE | 1 |
Number of fields for each RESOURCE | 25 |
Total number of fields | 250,000 |
Synchronization Time | under 2 hours |
Scenario 2: Importing a Single Project in Large Deployments | |
---|---|
Objects in Synchronization | Units |
Number of ACTIVITY (ies) | 5000 |
UDF CODEs for each ACTIVITY | 10 |
ACTIVITY CODEs for each ACTIVITY | 5 |
RESOURCE ASSIGNMENT | 1 |
Fields for each ACTIVITY | 30 |
Total number of fields | 150,000 |
Synchronization Time | under 2 hours |
Scenario 3: Exporting Projects in Large Deployments | |
---|---|
Objects in Synchronization | Units |
Number of PROJECTs with minimum fields | 500 |
Fields in each PROJECT | 7 |
Total number of fields | 3,500 |
Synchronization Time | under 15 minutes |