Same APP on WS2008 slower than on WS2003 - often.

[ThomasAJ]

New IBM X3200 server (their smallest but still Core 2 Duo), WS2008, 2GB RAM.
Terminal Services, 3 to 5 users.

Our main app often (but not always runs slower)
compared to when it was on IBM X206 (4 yrs old), WS2003, 2GM RAM.

Symptoms: when going from property to property using "next record" control
it often just 'freezes' for say 2 to even 10 seconds before going on to
another property. Yes there are lots of calculations and record reading in
preparation for displaying info on the next property but it was not a problem
on a lesser set up. The delay does not always happen when transitioning to
the same property.

I just did a test: I clicked on "next" over and over again - it went from
property to property quickly, Task Mgr showed about 30% CPU and then after
about 10 properties - froze for 8 secs - before going to other properties. I
then went backwards and it froze but not on the same property as before.

CPU usage actually goes down during freeze.

Sometimes the main window of the app even goes temporarily white (ish - like
a thin film cover).

Nothing else has changed - same few users - 3 to 5 over Terminal Services.

Task Manager does not spike in CPU usage, it just hovers around 15% (this is
on average during the day) mainly due to WmiPrvSE.exe.

I could increase RAM to 4GB.

This is difficult to track down - are there any appropriate forums for these
type of issues if there is no direct help here.

 

[david]

Doesn't look like an Access problem -- looks to me like a network
problem or a memory problem. Can you watch what is happening
with disk activity and disk cache and swap file and memory?

I think you should go to a TS group and a Network group and
a Server group to ask what you should be measuring.

(david)

 

[Tony Toews [MVP]]

New IBM X3200 server (their smallest but still Core 2 Duo), WS2008, 2GB RAM.
Terminal Services, 3 to 5 users.

Our main app often (but not always runs slower)
compared to when it was on IBM X206 (4 yrs old), WS2003, 2GM RAM.

Symptoms: when going from property to property using "next record" control
it often just 'freezes' for say 2 to even 10 seconds before going on to
another property. Yes there are lots of calculations and record reading in
preparation for displaying info on the next property but it was not a problem
on a lesser set up. The delay does not always happen when transitioning to
the same property.

What version of Access? Have the SPs been installed?

Here's one possible hotfix for A2007.

After you upgrade Access 2003 to Access 2007, operations on existing
forms have slow performance.
http://support.microsoft.com/kb/956054

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Paul Shapiro]

You can look at performance measures, but given the cost of ram, I'd start
by increasing to 4GB. 2GB would be ok for a single-user workstation, but
seems low for multiple users on a TS. The intermittent temporary freezing
could be paging, which you would probably see by looking at performance
counters.

 

[MikeB]

New IBM X3200 server (their smallest but still Core 2 Duo), WS2008, 2GB RAM.
Terminal Services, 3 to 5 users.

Our main app often (but not always runs slower)
compared to when it was on IBM X206 (4 yrs old), WS2003, 2GM RAM.

Symptoms: when going from property to property using "next record" control
it often just 'freezes' for say 2 to even 10 seconds before going on to
another property. Yes there are lots of calculations and record reading in
preparation for displaying info on the next property but it was not a problem
on a lesser set up. The delay does not always happen when transitioning to
the same property.

I just did a test: I clicked on "next" over and over again - it went from
property to property quickly, Task Mgr showed about 30% CPU and then after
about 10 properties - froze for 8 secs - before going to other properties.. I
then went backwards and it froze but not on the same property as before.

CPU usage actually goes down during freeze.

Sometimes the main window of the app even goes temporarily white (ish - like
a thin film cover).

Nothing else has changed - same few users - 3 to 5 over Terminal Services..

Task Manager does not spike in CPU usage, it just hovers around 15% (thisis
on average during the day) mainly due to WmiPrvSE.exe.

I could increase RAM to 4GB.

This is difficult to track down - are there any appropriate forums for these
type of issues if there is no direct help here.

That "whitish" screen that you describe sounds like Vista - Did you
upgrade to Vista? Then you definitely need more than 2GM [sic!)
memory.