Re: Slowly Terminal Server response

You can use (free) threadmater to cap the cpu usage on your access app:
http://threadmaster.tripod.com/

How much memory is left when the 20 sessions are running?

Regards,
--

Stefan Vermeulen
MVP - Terminal Server
http://www.printingsupport.com


"Thomas Kroljic" <tkroljic@xxxxxxxxx> wrote in message
news:OI6QQA%23MHHA.4712@xxxxxxxxxxxxxxxxxxxxxxx
All,
We have a Terminal Services server (w2k, 2gb RAM) running in application
mode. Recently, the server (the users response) has been running extremely
slow. We have about 20 users connecting to this server via a VPN
connection to our main server (SBS 2k3 R2) and then they connect to our
Terminal Server with the TS client software or Remote Desktop Connection
(should they all be
using the TS Client software and could this be the problem).

The application that the users are using is an MS Access applications.
Pretty simple: data entry forms, query listings, reports. Very low
transactional
application.
I went into the Task Manager and noticed that the spoolsv.exe is taking
up a large amount of memory. I quess my question is what should I be
looking for to
find out why the server is running so slowly?

Is there a good article on TS regarding system requirements for x amount
of users connecting?

Any help or guidance would be appreciated.

Follow-up info:

the CPU will peg at 100% sometimes for 10 - 20 seconds at a clip. The
culprits seem to be the Access applications (sessions).
This particular Terminal Server has 2 CPU chips (Dell P1400, SP4). Not
sure why the application would grab 100% of the CPU.
This is becoming a major problem for some of our users. Not sure where I
should be looking.
Is there a parameter that I can tweak to tell the CPU to only allocate a
certain amount of CPU time (cycle) per user at any given time?
Memory wise, each Access session seems to be taken up about 22,000k to
32,000k of Mem Usage.

Again, if there is a good white-paper on this issues or subject I'd be
glad to read it.

Sorry for double posting this issue. The last time I sent this in was over
a month
ago and I, yes I, never followed up on the response.

Thank you,
Thomas Kroljic



.

Relevant Pages

  • Re: for linux, which CPUs are almost always faster than which other CPUs?
    ... Is there any way to find out how to compare two different CPUs for the ... For a *web server*, the main bottleneck is you disk drives / mass storage ... The *second* bottleneck will be memory. ... And then I'll ask someone about comparing CPU A and CPU B, ...
    (comp.os.linux.misc)
  • Re: Slowly Terminal Server response
    ... physical memory is an indicator of available memory. ... If Task Manager only shows a single CPU graph, then only one CPU is installed. ... A good general guide to keep in mind is that most applications require the similar amount of memory as they would on a desktop for each user. ... I normally start with a general guideline of 25-30 concurrent users for a server with 4 GB of RAM and 2 CPUs and then do testing for a specific set of required applications. ...
    (microsoft.public.windows.terminal_services)
  • Re: 64-bit memory consumption
    ... CPU cores and memory keep pace with each other, ... There is time spent in GC that won't be affected only to the GC cycles, you get indirect hits in the form of poor cache coherency and cache pollution in the code that uses GC'ed memory. ... Desktop CPUs with significantly larger caches aren't there yet, and on a server, your cache is shared by multiple applications, and you can't appropriate it all for your application's purpose without affecting the rest. ...
    (borland.public.delphi.non-technical)
  • Re: CTRL-ALT-DEL SCREEN VANISHES
    ... for memory and CPU can give you an idea of what is going on. ... The server runs the following apps/services ... force the problem to occur making it more difficult to troubleshoot. ...
    (microsoft.public.windows.server.security)
  • RE: Performance Problem
    ... Generally Mingqing's reply is very helpful for troubleshooting SQL ... However, SQL Server 2000 ... Standard Edition does not support more than 2GB memory. ... When multiple access is concurrently executing, if 2 sessions are executing ...
    (microsoft.public.sqlserver.server)