Look through the logs to identify if the slowness is on the client side, or the server side. If you see a very long time between the time a query is sent to the server, and the time it is received, then you will know it is either server side, or an issue with the network.
Next, you can go to the server side, and monitor the duration it takes for the query. If the duration on the server is short, then this should narrow it down to something on the network. Thanks, Gary Opela, Jr., RSP Remedy Engineer Leader Communications, Inc. http://www.5pointleader.com http://www.lcibest.com Best Product, Best People, Best PriceTM An ISO 9001:2000 Certified, CMMI(r) Level 3 Rated Company -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of T. Dee Sent: Thursday, June 26, 2008 1:14 PM To: [email protected] Subject: Re: Remedy - sensitive to network performance? Do you have your users running reports during business hours? This can slow down Remedy quite a bit - unless you have a dedicated reporting server. Or perhaps you have users running unqualified searches - that will also impact performance. On 6/26/08, Dave Wilmot <[EMAIL PROTECTED]> wrote: > ** > Dave, > > Your systems administrator(s) should easily be able to isolate the network > as the problem (or not) by running one or more utilities which will check > network "round-trip" times. One such tool might be the Solaris (Sun Unix) > "ping -sRv" command, which shows trip times to each "hop" or "router" on the > way to the remote location/server. > > I've been out of the systems-admin world for many years now so my command > options above may not be perfect. Talk to your system administrator(s) and > as them to check the round-trip times for you. If there is an obvious > problem with the network performance, it should show up in the output > generated by the "ping" test, or an equivalent command/utility. They > probably have a network monitoring application as well which would could be > used to perform the same or similar test. > > Finally, the question still exists as to what is an acceptable transaction > time for a network packet to travel about on the network. That is really > something each company must decide for themselves. Your S/A should be able > to give you a good general understanding of what to expect on a well-tuned > WAN (all depends on your infrastructure). > > Don't forget to check the load on the various servers. You could have a WEB > server, database server, application server, etc which may be bogged down. > > Best of luck, > > Dave Wilmot > > > > Dave Wilmot > President > Rapid Technologies > 303.948.1014 ext 101 > 303.948.1614 (fax) > [EMAIL PROTECTED] > www.raptek.com > ________________________________ > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Barber, David > Sent: Thursday, June 26, 2008 7:12 AM > To: [email protected] > Subject: Remedy - sensitive to network performance? > > ** > > Hi, > > Has anyone experienced end-user performance problems with Remedy over larger > networks? > > We're running a suite of bespoke applications, and are finding that some > tasks such as opening/updating incidents can take orders of magnitude longer > in some locations. For example it can take me 8 seconds, but a colleague at > another location 2 or 3 minutes. > > Have been able to do some local benchmarks - typical ping responses are > circa 10ms, but at points when we find that even our performance is hit, we > find the network is responding to pings at maybe 60+ms. Our network guys > invariably say that the network is running fine ... > > So it appears that Remedy, or at least the applications we're running, are > incredibly sensitive to network performance. Any suggestions from the list > as to what we can do to improve performance? > > Regards > > Dave > This e-mail has been scanned for viruses by the Cable & Wireless e-mail > security system - powered by MessageLabs. For more information on a > proactive managed e-mail security service, visit > http://www.cw.com/uk/emailprotection/ > > The information contained in this e-mail is confidential and may also be > subject to legal privilege. It is intended only for the recipient(s) named > above. If you are not named above as a recipient, you must not read, copy, > disclose, forward or otherwise use the information contained in this email. > If you have received this e-mail in error, please notify the sender (whose > contact details are above) immediately by reply e-mail and delete the > message and any attachments without retaining any copies. > > Cable and Wireless plc > Registered in England and Wales.Company Number 238525 > Registered office: 3rd Floor, 26 Red Lion Square, London WC1R 4HQ > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ > __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" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
