DCR lock performance issue

Hi,

I have a query.

Currently in my production TS6.1 CMS server on Solaris8, we have nearly 8000 DCRs(roughly). Out of which apprximatel 4000+ DCRs are locked by users.

Will there be amy impact in performance beacuse of the above scenario. If yes, do you have any formula to compute the performance issue based on more number of DCRs in locked status.

Appreciate your help.
Exceptional case :
On repeated training provided to our business users on DCR lock issue, we couldnot reduce this number.

Find more posts tagged with

Comments

nipper

There is not a serious performance issue in this case, inless you decide to do a view locked files. That wil take some time.

Now my question is why there are so many locked ? If there are files that have been locked for months (or years) at a time, then there is something wrong with the implementation. Does you workflow remove locks ?

Andy

chicka

Our business user's are mainly from third party company and they used to have acces to our CMS server for a limited duration.

Once the site is launched, we used to remove the access for those userids. At this point user's would have created 2000 DCRs out of which only 500 DCRs would have got submitted to STAGING environmnet. So rest of the DCRs will have a lock status tied up.

This is the case for all the branches in our CMS server. We don't have any default WF to submit the files which have lock status for stipulated period.

I have a plan of writing a perl script to unlocj the DCRs which are older than 6months. Is this the right way to improve our CMS performance.

Also my doubt on lock issue has been arised because of the below article..
"Knowledge Base Article: 1553 "

nipper

OK then, what locking model are you using ? Submit is the most common and it is not affected by this issue.

That KB is also several years old and may be out of date.

Andy

chicka

yes, my project uses submit locing model.