Re: Slowly Terminal Server response
- From: "guyyardeni" <guyyardeni@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 9 Jan 2007 20:04:56 -0800
Yes, physical memory is an indicator of available memory. You can also take a look at the size of the paging file, when that starts to go up the server will slow down due to page fault activity.
If Task Manager only shows a single CPU graph, then only one CPU is installed.
As far as the recommended amount of memory, it greatly depends on how many and what type of applications your users are running. 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. While there are some savings in the multi-user environment in my experience they are not significant for most applications.
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.
--
Guy Yardeni
"Thomas Kroljic" <tkroljic@xxxxxxxxx> wrote in message news:OYzFjNENHHA.4928@xxxxxxxxxxxxxxxxxxxxxxx
Not sure how to determine the amount of memory left when the max amount of users are connected. What number should I be looking at? Should I be looking at the number under the "Physical Memory (K)" - Available ???
Also, I'm starting to think that this box only has 1 CPU. The owner said that he ordered a second CPU several years after the initial purchase (Dell P1400). He said that his had a problem installing the chip and had to have a Dell Tech come to the office with a new MotherBoard. How can I tell if the box is using one or two CPUs? If I go into the Task Manager, under the Performance tab, the CPU Usage History only shows one CPU and the View/CPU History option does not give me an option to see two separate graphs.
Thanks,
Thomas Kroljic
"Stefan Vermeulen" <stefan@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:45a3feb0$0$336$e4fe514c@xxxxxxxxxxxxxxxxxYou 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@xxxxxxxxxxxxxxxxxxxxxxxAll,
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
.
- Follow-Ups:
- Re: Slowly Terminal Server response
- From: Thomas Kroljic
- Re: Slowly Terminal Server response
- References:
- Slowly Terminal Server response
- From: Thomas Kroljic
- Re: Slowly Terminal Server response
- From: Stefan Vermeulen
- Re: Slowly Terminal Server response
- From: Thomas Kroljic
- Slowly Terminal Server response
- Prev by Date: Re: Slowly Terminal Server response
- Next by Date: Terminal service settings on NT4
- Previous by thread: Re: Slowly Terminal Server response
- Next by thread: Re: Slowly Terminal Server response
- Index(es):
Relevant Pages
|