One other thing I would check is the number of Fast/List Threads. If you increase them that may improve performance.
Also you may want to see if you have any custom workflow that is running in a infinite loop. This can cause all of your fast/list threads to be consumed and cause poor performance in ARS. Sean From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of SriSamSri Appecherla Sent: Monday, July 12, 2010 11:33 PM To: [email protected] Subject: Re: Poor performance while saving Incidents ** Hi, As per my logs I have problem only with CLOB storage. It is a new set up and so no new indexes have been created. Satish, Can you please give more info on on the PropConvertor? Regards, SriSamSri Appecherla Mobile# +91 991 610 6008 On Tue, Jul 13, 2010 at 11:56 AM, SUBSCRIBE arslist Sathish <[email protected]<mailto:[email protected]>> wrote: Adding up to Sean's comment, i remember running the utility named "PropConvertor" which basically is pl/sql procedure that converts all the existing CLOB from outrow to inrow. This helped us in having better incident save time + the restart time of the server. Regards Sathish _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org<http://www.arslist.org/> attend wwrug10 www.wwrug.com<http://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"
