If projects routinely include a very large number of assets—for example, 10 thousand or more—you should optimize asset locking by setting two VersionManagerService properties as follows:
Property | Setting |
|---|---|
| true |
| Set to the desired threshold. A setting of 0 ensures that optimized asset locking is always in effect. |
Also, disable secure repositories by removing the applicable secured versioned repositories from the VersionManagerService’s versionedRepositories property and specifying the corresponding unsecured versioned repositories instead (see Disabling a Secured Repository).
The number of project assets that might require optimization can vary, depending on other site-specific factors such as processing speed and network load.
