Find where it's slow, then make it faster. Is that on queue? Places to look: - db queries (indexing, find full table scans and fix them) - db tuning (cursor sharing, lob storage, etc.) - network performance (for various critical communication paths) - app design (server vs. client workflow) - data model (what % of cpu time is used just copying the same data over and over again)
Axton Grams On Mon, Jul 28, 2008 at 11:14 PM, patrick zandi <[EMAIL PROTECTED]> wrote: > ** > no more than 7 indexes of any kind on any 1 form that is for submitting - > (makes the creates faster) > 15 for history (archived) > > I have 12 more... That I know others will share. > > =8-) > > On Mon, Jul 28, 2008 at 9:47 PM, sam appecherla <[EMAIL PROTECTED]> > wrote: >> >> ** >> Hi, >> >> Can you please suggest me some performance improving tips in Remedy? >> Regards, >> SriSamSri Appecherla >> Mobile# +91 991 610 6008 >> __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" >> html___ > > > -- > Patrick Zandi > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
