Also, Check you indexes on things like AR System Message Catalog, and the Help desk form. Our otb Help Desk form had 16 indexes on it (17 if you count entry id). That will cause slowness on a save.
Danny, We have been having performance problems as well (same versions too) Usually it has to do with someone running a bad query and locking the table. Or fields not getting set, and then a table using an external table qualification with an empty field (translates it into 1 = 1) Any documentation you have I would be very interested in. Thanks, Matt P. From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Danny Kellett Sent: Wednesday, May 12, 2010 9:58 AM To: [email protected] Subject: Re: Question on Remedy Performance ** The AR system is very latency bound. E.g. if your end users have a latency above 40ms, then you will start to notice a performance hit. Also, ITSM applications at that version was not built for performance but functionality. I have done some work on this and I am happy to share some documents with you off list. Some of the obvious things that were done include removing the option on "Refresh on entry change" on the tables within the incident form. For example if I remember there were approx 5 tables, so when you open / select an incident, all those refreshed when in reality, you won't want to see the financial information every time etc. Send me an email and I will dig out the docs for you. dkellett (at) javasystemsolutions.com Kind regards Danny Kellett SSO for ARS http://www.javasystemsolutions.com/jss/ssoplugin From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Jim Coryat (jcoryat) Sent: 12 May 2010 15:35 To: [email protected] Subject: Question on Remedy Performance ** We are running ARS 7.1 patch 006 with ITSM 7.0.03 patch 007. The applications for the most part have been out of the box implementations, we have made some customizations but they have been minor in scope. Our application servers are dual 3.0ghz Xeon boxes with 8gb of memory running windows 2003 Enterprise. The database is Oracle 11 on a Sun V440 4 CPU 32gb memory dedicated box. Both the application server and database are on gigabit network connections. This has been bugging me for a while and I can't seem to figure out why the application server and database for the most part sit there at an idle, yet we have lackluster performance of the remedy system in regards to the customer experience on the desktop and web client. The performance is not terrible, however due to the under utilization of the hardware I would expect better response than what we are seeing. What I'm looking for is some pointers or documentation someone might know about that would help to identify anything that would be causing this behavior. I have read the scalability white papers published by BMC, which closely mirrors our configuration and this has been of little value. Jim Coryat Micron Technology Inc. _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
