Windows Terminal Server - V8 Performance issues

Todd -

If you are using the default Windows RD Client, try turning off all the
fluff features such as menu animation, etc... and see if that speeds
performance.

Daniel Tisone
dan.tisone@...


-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Todd Anderson
Sent: Friday, September 08, 2006 6:02 PM
To: 'Vantage @ YahooGroups. Com'
Subject: [Vantage] Windows Terminal Server - V8 Performance issues

Ok, did some testing today on V8 over a WAN using Windows Terminal
Server.

Given a T-1 VPN link testing at about 950K point to point after the
encryption penality.

Distance ... About 100 miles ...

WT server is a P-3.0/2 gig

Local PC's at almost any speed work great via WTS. Screens "pop" up
nicely
and V8 performance is --much-- better then direct PC connections when
the
local PCs are sub-P2.0 ...

However, the remote facilities test using a P-3.0/2-gig PC at the remote
gave the following response ...

Running V8 locally/@remote ... (1) Screens loaded -reasonably- quick
although there was a obvious delay caused by retrieval of data from the
remote server. (2) On the other hand - tabbing through fields and data
entry was smooth and quick including scrolling through retrieved
records.

Running V8 via WTS ... (1) Data loaded much quicker (2) All screens
exhibited a top to bottom lag in filling in the screen. Like running
PC-Anywhere over a really slow modem. They could watch the screens
being
"Painted" top to bottom. (3) Once loaded - using a right side windows
scroll bar was very slow to refresh screen image and (4) Tabbing
through
fields and data entry had a slight but annoying delay.

Tried running WTS at lowered screen colors to no avail.

End user's response ... I'd rather deal with V8 running locally with
slow
data access then deal with watching the screens paint ...

My past experience is that a true windows "terminal" runs very nicely in
this situation.

Has anyone found a way to get a local PC, given reasonably decent specs,
to
perform on par with a windows terminal in terms of it's ability to
handle
WTS?

Also, I don't suppose anyone has a SQL DB with say ... 10,000+ parts,
2,000+
vendors, 2,000+ customers, and a boatload of shop orders / operations
that
they would like to share??? I'd love a test DB with some real world
data
in it to use for performance testing ...

Thanks,

Todd Anderson



Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder
and Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/links
Yahoo! Groups Links
Ok, did some testing today on V8 over a WAN using Windows Terminal Server.

Given a T-1 VPN link testing at about 950K point to point after the
encryption penality.

Distance ... About 100 miles ...

WT server is a P-3.0/2 gig

Local PC's at almost any speed work great via WTS. Screens "pop" up nicely
and V8 performance is --much-- better then direct PC connections when the
local PCs are sub-P2.0 ...

However, the remote facilities test using a P-3.0/2-gig PC at the remote
gave the following response ...

Running V8 locally/@remote ... (1) Screens loaded -reasonably- quick
although there was a obvious delay caused by retrieval of data from the
remote server. (2) On the other hand - tabbing through fields and data
entry was smooth and quick including scrolling through retrieved records.

Running V8 via WTS ... (1) Data loaded much quicker (2) All screens
exhibited a top to bottom lag in filling in the screen. Like running
PC-Anywhere over a really slow modem. They could watch the screens being
"Painted" top to bottom. (3) Once loaded - using a right side windows
scroll bar was very slow to refresh screen image and (4) Tabbing through
fields and data entry had a slight but annoying delay.

Tried running WTS at lowered screen colors to no avail.

End user's response ... I'd rather deal with V8 running locally with slow
data access then deal with watching the screens paint ...

My past experience is that a true windows "terminal" runs very nicely in
this situation.

Has anyone found a way to get a local PC, given reasonably decent specs, to
perform on par with a windows terminal in terms of it's ability to handle
WTS?

Also, I don't suppose anyone has a SQL DB with say ... 10,000+ parts, 2,000+
vendors, 2,000+ customers, and a boatload of shop orders / operations that
they would like to share??? I'd love a test DB with some real world data
in it to use for performance testing ...

Thanks,

Todd Anderson