| Author |
NT workstation vs NT Terminal Server
|
|
| Kurt Remlin 2005-03-15, 3:55 pm |
| Hi,
We have Clipper 5.2e + Blinker 7.10 DOS application that is accessed
from local workstations and remotely via Terminal Server. The
executable and data resides on Novell Netware 4.11 file servers.
Workstations and Terminal Servers are based on Win NT 4. There are
several different installations that use this architecture.
We've been presented with the situation when a certain part of the
application runs incomparably slower for remote (Terminal Server) users
than their local counterparts. This situation have been reported for
multiple installations. The slowness itself does vary. In some
measurements the process that used to take less than a minute clocked
at half an hour.
Users claim that this disparity started after our latest maintenance
update. We analyzed the code changes between releases and did not find
anything obvious.
Allegedly no changes have been applied to the servers at that time.
Our application runs in protected mode and we do not store any data on
the local drives. We do not have TEMPPATH and SWAPPATH burned in in
the link script.
I'm presently at loss. While network guys promised to sniff the lines
and do their part I am not sure what to look for.
Is there a Clipper code that will run slower on a Terminal Server than
on a similarly configured workstation?
| |
| Nick Ramsay 2005-03-15, 8:55 pm |
| On 15 Mar 2005 10:25:46 -0800, "Kurt Remlin" <pm771@netscape.net>
wrote:
>Is there a Clipper code that will run slower on a Terminal Server than
>on a similarly configured workstation?
Anything which forces lots of screen updates will be noticeably slower
on a TS link.
| |
| Kurt Remlin 2005-03-15, 8:55 pm |
| Nick,
Thank you very much for the reply.
<<< Anything which forces lots of screen updates will be noticeably
slower on a TS link. >>>
The delay is actually between the screens.
| |
| Kurt Remlin 2005-03-15, 8:55 pm |
| Another bit of information.
We asked users to try running the app on the Terminal Server itself,
not through the client. It was still slow. Normal workstation was
still fast.
| |
| Kurt Remlin 2005-03-18, 3:55 pm |
| <<< I only have blinker 7.00 >>>
You're right. It was a typo.
| |
| Andreas Moroder 2005-03-23, 3:55 am |
| > Is there a Clipper code that will run slower on a Terminal Server than
> on a similarly configured workstation?
>
Hello,
what about to link into your app Dave Pearson's oslib and call the yield
function in loops that wait on keyboard input.
In windows 2000/Xp Dos application that loop waiting for a keyboard
input eat app 100% of cpu resources. On a terminal server one single
clipper app that waits for a inkey() can slow down the whole machine.
Bye
Andreas
| |
| Kurt Remlin 2005-03-23, 3:55 am |
| <<< I only have blinker 7.00 >>>
You're right. It was a typo.
| |
| Alwin Nederpelt 2005-03-23, 3:55 am |
| I only have blinker 7.00
do you have an update for me ???
alwin
On 15 Mar 2005 10:25:46 -0800, "Kurt Remlin" <pm771@netscape.net>
wrote:
>Hi,
>
>We have Clipper 5.2e + Blinker 7.10 DOS application that is accessed
>from local workstations and remotely via Terminal Server. The
>executable and data resides on Novell Netware 4.11 file servers.
>Workstations and Terminal Servers are based on Win NT 4. There are
>several different installations that use this architecture.
>
>We've been presented with the situation when a certain part of the
>application runs incomparably slower for remote (Terminal Server) users
>than their local counterparts. This situation have been reported for
>multiple installations. The slowness itself does vary. In some
>measurements the process that used to take less than a minute clocked
>at half an hour.
>
>Users claim that this disparity started after our latest maintenance
>update. We analyzed the code changes between releases and did not find
>anything obvious.
>
>Allegedly no changes have been applied to the servers at that time.
>
>Our application runs in protected mode and we do not store any data on
>the local drives. We do not have TEMPPATH and SWAPPATH burned in in
>the link script.
>
>I'm presently at loss. While network guys promised to sniff the lines
>and do their part I am not sure what to look for.
>
>Is there a Clipper code that will run slower on a Terminal Server than
>on a similarly configured workstation?
|
|
|
|