Win2k3 TS intermittent performance issues

  • Thread starter Thread starter David S
  • Start date Start date
D

David S

Guest
We are running Win2k3 TS on a dual quad core 2.66gHz with 4GB RAM and RAID 5
setup. We have about 10 users who connect to the server to run Access 2k3
databases and some SQL 2000 database functions.

We are experiencing intermittent perfomance issues. Example 1: A user opens
an Access db, one time it opens quickly (under15 seconds) another time it
takes over 2 minutes to open. A user runs a query, one time it runs quickly,
another time the exact same query takes over 2 minutes. Example 2: When
browsing a directory tree either in Windows Explorer or an Open File dialog
box, there is a noticable delay when trying to expand trees or when clicking
on a folder.

TIA
David S

One thing I tried to correct the issues was to create a page file on each
logical drive (2046-4092). This seemed to help, but the issues resurfaced
after a few days. I also tried monitoring disk access and memory using
Performance Monitor. As far as I could tell, everything looked fine and there
didn't appear to be an excessive load on the server. Memory and disk access
jumped when running Access, but it didn't look out of the ordinary.

Does anyone have any ideas or suggestions as to what else I can look at? Is
there a good TS Performance Tuning paper out there? Also, when checking for
disk or memory issues, what are the best counters to monitor?
 
Re: Win2k3 TS intermittent performance issues

This smells like a problem with the connection to the server. an RDP
session is very good at tolerating packet loss. I'm going to bet that
when the slowness occurs, you can't move any window around (such as
explorer) ??

I recently discovered just how "good" ts is at tolerating packet loss
with out causing a disconnect...we had a T1 terminating in a cisco
router...the WIC card was loose or something, the T1 was flapping;
going up and down and up and down very rapidly...TS seamed to be very
slow and jerky during this, in the end nothing was wrong with the
server at all.
 
Back
Top