Site Studio Performance Issues —Lock Contention with ssLink and ssNodeLink
(Doc ID 951949.1)
Last updated on OCTOBER 11, 2017
Applies to:Oracle WebCenter Content - Version 10.1.3.3.3 and later
Information in this document applies to any platform.
While profiling UCM during a small load test we noticed that around 50% of the elapsed time is spent while waiting on a read lock of the project file(SSHierarchyServiceHandler.reserveSiteInfo(...)). The origin of the read lock seems to be the idoc functions ssLink and/or ssNodeLink.
If each link acquires a lock on pages which contain many links and where the links are generated by ssLink/ssNodeLink calls inside a datafile, the performance of the system can degrade significantly.
- What is the reason that ssLink calls acquire a lock on the project file?
- How can subsequent lock acquisition in the same request be avoided?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document