Re: Slow Performance issues



I really appreciate all the comments and will look at the things that have
been mentioned, but I did some additional testing today and found something
interesting. Most of the users are connecting to the Terminal Server via
the LAN (the client machines and the TS are on the same LAN running through
a 10/100 switch) and are using PC's with the Terminal Services Advanced
Client to connect. Others who have PC's are using the Remote Desktop
Connection software. Both of these groups are seeing the slow performance
that I've described.

Four of the users at the site have Thin Client Terminals (HP T5520) instead
of PC's. Those users do not seem to be having any of the slow performance
issues that the other users are experiencing.

Could the performance issues be related to the workstation configuration or
the software client?
Most of the workstations are Windows XP with 256MB RAM, and have previously
been used as PC's so they've got plenty of junk on the hard drives.
However, we are not seeing the performance issues when Word or other
programs are being used on the local machine.

Thanks again for your help.
--David


"network_ninja" <networkninja@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6CB4CD42-A045-4D22-A39F-6D491D730E41@xxxxxxxxxxxxxxxx
Yes, powerful boxes yet getting performance issue for light users doing
very
simple tasks?

Yes, could be network related as mentioned already.

Still, could be something happening within the server itself? - i can see
CPU and Memory has been suggested also.

My thoughts are; within the server you are sharing resource between the 15
users you have mentioned. Now, all users may be doing differnt things,
some
may be running same applications, some running same tasks... Fact is,
within
your task manager you are going to see the Windows Scheduler changing the
priority of the running proccesses. It may be worth looking in here.

If a user were to do something that was a litte more resource intensive,
and
was wanting to consumer more CPU time than normal, it is knowned that the
Scheduler will see this larger process and as a result, may in fact
prioritise in order to complete the task as soon as possible. It is at
this
point the other, lighter users will start to feel the hit. Anyone simply
typing and doing admin work will be seen as a lower priotiy and so will
recieve lower priority within the CPU running process queue.

The heavy user does not feel the hit as he is getting ample CPU time and
priority, everyone else at this point can see latency on the smaller
tasks.

There are ways of controlling these running processes, this may first of
all
eliminate some of the isssue, following on from that some vendors claim to
not only smooth out the performance, but also have a faster running server
due to reduction in CPU queue lengths...

Monitoring tools such as EdgeSight may point out what is happening.. great
for figuring it out, but guessing you may need something to actually
control
what is happening...

"David G. Hoch" wrote:

We've got a terminal server environment which contains a Small Business
Server and Terminal Server. Both boxes are very powerful (Dual-Core
Xeon,
4GB RAM, 15000 RPM SAS RAID array, etc). There are only about 15 users
on
the system and most of those are very light users (i.e. e-mail, Word, web
browsing).

I'm getting complaints of slow performance, particularly in MS Word.
People
are seeing keyboard lag while typing into MS Word, or into Outlook e-mail
messages (which is using Word as its editor).
I've also gotten complaints that when highlighting sections of a word
document (using Shift-Click) there is a long lag.

A couple of the workstations are HP Thin Client terminals, but the
majority
are PC's running Windows XP. The users are connecting via Terminal
Services
Advanced Client rather than RDP.

Any thoughts about what might be causing slow performance would be
greatly
appreciated.

Thanks,
--David





.