Rick:
I agree. However, the MT server is on a different continent. This is why I think the fat-long problem associated with RPC traffic happens. (If you need more information on this, look for the Riverbed traffic shaping device, they have a real good explanation on this problem.)
This is made worse by the methods used by MT 6.3 + to transfer traffic from the ARS server to the MT server.
James McKenzie
L-3 GSI
________________________________
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Rick Cook
Sent: Tuesday, October 17, 2006 7:57 AM
To: [email protected]
Subject: Re: Mid Tier - Long Applet Load Time
**
I agree that her network is a concern, but the pre-caching should at least isolate that as the source of any remaining lag time.
Perhaps if they added a second web server closer to the clients, and pre-cached to that, it would take care of the problem either way.
Rick
On 10/17/06, McKenzie, James J C-E LCMC HQISEC/L3 <[EMAIL PROTECTED]> wrote:
**
Rick:
I think the problem is due to the method used to move information from the ARS server to the MT server for forms and workflow. This is not so obvious when the two are located on the same network segment but can become very visible when the ARS server and MT server are separated by a great distance. This slows down form loading to a crawl. Of course there is a script or program that can force the MT server to 'pre-cache' once the cache is flushed. This may or may not solve Jamie's problem...
James McKenzie
L-3 GSI
