Hi guys, Hope you all are having a great day.
I have an slight issue and some questions that I hope someone could help shed some light on before I take this to BMC support. Recently, we did some group changes via the group form which caused a group-cache update to be performed on the servers. During this time, the CPU of our first server jumped to 90% and sustained that for at least 3-4 minutes. During this time no user could operate in Remedy at all. All other operations came to a screeching halt while this was being done. Is this the norm for a group-cache update? I thought I read in the docs that when a group-cache update occurs, only the admin thread is used and should not affect other list and fast threads from using the system. There will be some performance impact, but no where does it state the system will come to a halt when it's performed. We have also seen this same behavior when modifying a piece of workflow. Though I can understand this happening when we modify workflow to some point as the server needs to recache workflow objects. The thing is, my coworker has worked on other Remedy projects with other companies and hasn't seen this behavior at all. On our most loaded days we only have 170 people accessing remedy. Is this a configuration issue? Has anyone else seen this behavior? My servers are as follows: 2x Sun Fire v480R 1.2 Ghz 4GB RAM Sun Solaris 9 SPARC AR System 6.3 patch 20 server group Database Server: SunFire v210 1.3Ghz 8GB RAM Sun Solaris 9 SPARC Oracle 9i -- "A fool acts, regardless; knowing well that he is wrong. The ignoramus acts on only what he knows, but all that he knows. The ignoramus may be saved, but the fool knows that he is doomed." Bob Halstead _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
