README VERSION : 1 README Creation Date : 2011-09-19 Patch-ID : 143682-03 Patch Name : VRTSglm 5.1SP1RP2 BASE PACKAGE NAME : VRTSglm BASE PACKAGE VERSION : 5.1 Obsolete Patches : NONE Superseded Patches : 143682-02 Required Patches : 143682-01 Incompatible Patches : NONE Supported PADV : sol10_x86 (P-Platform , A-Architecture , D-Distribution , V-Version) Patch Category : PANIC , PERFORMANCE Reboot Required : NO FIXED INCIDENTS: ---------------- Patch Id::143682-03 * Incident no::2406572 Tracking ID ::2146573 Symptom::Customer reported this as performance issue. The application was running slower when this problem happens. The SAR utility on HP-UX was showing some processes in PRI state. Description::(1) Complexity: This is an extremely complex performance concern in an environment where different applications are in great competition for the same system-wide resources. (2) Performance overheads: Competition for system resources is expected. However intense competition can create large overheads due to increased repetitive initialization. We approached this issue in multiple ways. Provided customer some tuning and application changes. Resolution::No product bug was identified from Symantec side. However a GLM patch was provided to customer which does two things. 1. Different names given to different GLM spin locks. So that we can identify various locks from spin watcher output. 2. We take avoiding a spinlock which keeps accounting if how many times allocation did in GLM. Removing this lock will not cause any regression. Also, we have not said that it will solve this performance problem.