Access 97 uses 100% cpu under win2k3 server

[Darrell Schroeder]

We have recently upgraded a client from a Windows NT
TSE/Citrix Metaframe server to a Win 2003 server with terminal services.
The hardware is a dual processor machine with HyperThreading enabled, so
four CPUs are visible to Win2k3. One of the applications the client
uses is a 16 bit app accessing an Access 2.0 database. We also have
custom extensions written in Access 97 which access the same Access 2.0
databases. We are now in the tuning phase of the upgrade, trying to
make sure that the performance is at least as good as the previous
system.

Here's the problem. Since the upgrade, each instance of the 16 bit app
runs at 100% of one of the virtual CPUs regardless of the actual
workload. Also, each instance of MSACCESS runs at 100% of a virtual CPU
for a fixed period of time after it does any work, after which it sleeps
at 0% until the next keystroke/mouseclick.

My question is, is this normal behaviour in a Win2k3 HyperThreading
environment? Or does this indicate a problem that we need to work out,
perhaps by pushing the client to upgrade to newer 32 bit apps?

D.

 

[John Spencer (MVP)]

Probably not a problem. Access does tend to grab all available CPU time, BUT it
is very compliant about releasing the CPU to other applications as needed.

 

[Darrell Schroeder]

Thanks. After additional testing that was the conclusion we came to.
But it's always nice to get someone else's opinion.

D.