Kevin,

You might take a look at the network round trip times. In my old Solaris
days you could run a "ping -sRv insertremotehostnamehere" command, to
check the network path and performance. Look at the milliseconds to
determine how the network connection is performing. Traditional 10-Megabit
Ethernet runs @ about 3-5 millisecond times between hops and/or gateways. A
WAN link is theoretically slower in most cases depending on the network
topology.

Find the equivalent command for your O/S. If the round trip times are
running in the hundreds or worse yet thousands of milliseconds, the network
may in fact be the limitation. You might be able to see which connection is
slowest. For example, say there are 5 hops between the client and the
remote server (5 gateways). If the milliseconds between node 3 and 4 is
noticeably slower than the others you can put your finger on the weak link
and then work with the network and systems people to see if the connection
can be optimized.. It is also quite possible there is a better or shorter
path to the remote host via another route. More often than not there is
more than one path to a remote host as the internal network has numerous
routers on it. You might check with your network person if you haven't
already to see if there is a "better" path to the remote host.

I agree with Davin's point.... anything above 200-300 milliseconds starts to
get REAL slow for most applications.

Good luck!

Dave Wilmot
Rapid Technologies
A Remedy Alliance Partner Since 1996
www.raptek.com

----- Original Message -----
From: "Kevin"
To:
Sent: Saturday, January 03, 2004 5:26 PM
Subject: Re: Remedy WAN issues


> Thanks for all your input folks. Some interesting suggestions i most
> certainly will be looking into, as well as sharing your personal
experiences
> in this area.
>
> Hoping 2004 is a good one for all of you...
> .and that the Remedy product moves onwards and upwards for the benefit of
us
> all!
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList)
> [mailto:ARSLIST@ARSLIST.ORG]On Behalf Of Davin Lindner-Green
> Sent: 29 December 2003 22:02
> To: ARSLIST@ARSLIST.ORG
> Subject: Re: Remedy WAN issues
>
>
> Although I am no networking expert, I have found that a more critical
> measurement than bandwidth is the latency of the WAN link. Latency is the
> time it takes a packet to traverse the link, including any routers or
> concentrators along the way. This is roughly the "ping" round trip time,
> and is usually measured in milliseconds (ms). I don't suspect that
> generally packet sizees are large for Remedy traffic hence little
> dependency on bandwidth.
>
> Remedy is an interactive application, in both native client and web client
> forms. A return key, menu selection or button click will require an event
> be sent back to the server and a response. So, you can add the latency x 2
> as a round trip delay between action and response, on top of processing
> time on the server/database/client. If you latency is 50ms, you might not
> notice the addtional .1 sec delay, but if your latency is at 600ms, the
1.2
> sec of addtional delay can add up fast. If I recall a rule of thumb,
> between 100-200ms is when you start getting into trouble.
>
> For users with extremely slow links, you may have to go with a non-
> interactive interface, such as email, since this does not depend on client
> to server communication in real time. Using email engine, you could allow
> for query, submit and update for these users. Of course, for such a WAN
> link, any interactive product would suffer the same fate as Remedy, so it
> would be a problem those users no doubt are dealing with today with your
> other applications.
>
> HTH,
> Davin
>
>

>
> UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
> mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
> www.QMXS.com
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.551 / Virus Database: 343 - Release Date: 11/12/2003
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.557 / Virus Database: 349 - Release Date: 30/12/2003
>
>


> UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
www.QMXS.com
>