Slashdot Mirror

← Back to Stories (view on slashdot.org)

Setting CPU Priority on NT/Citrix?

Posted by Cliff on from the preventing-bad-apples-from-spoiling-the-whole-bushel dept.

Broue Master asks: "I was recently faced with the task of finding a way to prevent some users from taking 100% cpu time in Citrix. I'm no MS certified anything (but I am a Citrix certified admin) and I couldn't find a built in way to do this. After someone on the NTSysAdmin List suggested trying to set the CPU priority to low from the command line, I investigated and found a small freeware that did the trick: PrioSet. I don't have a big user base: 3 power users (who are my problem with their Access and Excel use) and 10 regular users (and the people most affected by the problem). I'd like to know if any of you have previously tried this software, or if you've run into the particular problem when one user is getting 99% of the CPU for a long time while all other users only share the spare 1%. Did the software solve the problem or did you solve the situation by other means?"

8 of 48 comments (clear)

  1. command line by sql*kitten · · Score: 3, Informative

    After someone on the NTSysAdmin List suggested trying to set the CPU priority to low from the command line, I investigated and found a small freeware that did the trick: PrioSet.

    Type start /? into the prompt - it can start processes at different priorities. So you can replace direct shortcuts to your applications with .bat files that in fact start the application at a different priority.

  2. Easy by duffbeer703 · · Score: 3, Informative

    Change the shortcut that users launch Access & Excel with to point a CMD, shell or Perl script that launches Access or Excel, then sets drops the priority. It's pretty easy to use Perl to launch and control office applications.

    Another route may be to move the access database to an RDBMS, which may use less CPU horsepower than using Access as a client/server.

    --
    Conformity is the jailer of freedom and enemy of growth. -JFK
  3. Might not apply, but by Asprin · · Score: 4, Informative


    If the problem is 16 bit DOS apps, Tame can help.

    Also, when you installed Office, did you run the appropriate app-tuning script afterward? (Search in x:\wtsrv for *.cmd and you'll find a whole bunch of them.) These scripts can make a big difference with certain versions of Windows.

    You might also try the MetaFrame Installation and Tuning Tips. You might find a more recent version if you dig around.

    --
    "Lawyers are for sucks."
    - Doug McKenzie
  4. Throttle the processes programmatically by m8pple · · Score: 2, Informative
    If you have a bit of C knowledge then you could write something to throttle the processes back via API calls. Simplest would be to find all the access processes (via toolhelp), then every once in a while enumerate all the threads in each process and suspend them for a fraction of a second (SuspendThread/ResumeThread).

    As long as the suspensions are done quick and often there is usually no visible difference, except that the process takes a lower percentage of cpu time. Admittedly I've only used this sytem before to make processes self throttling, but there is no reason why it shouldn't work for third party processes.

    Obviously it would take a bit of tuning to get right, particularly if the access processes aren't competing with anything else most of the time, but it shouldn't take more than a hundred lines of code.

    Erm, yeah, or you could just run them at a lower priority.

    1. Re:Throttle the processes programmatically by borgboy · · Score: 4, Informative

      Actually, if he's running Win2k server, he can use the Job Object API
      This API allows you to set per-process limits on cpu, memory, user mode execution time, min/max working set, processor affinity, thread priority, UI restrictions, and security restrictions.
      I believe that Win2k Datacenter Server comes with a Job Object MMC for creating Job Objects / adding processes to a Job Object.

      --
      meh.
    2. Re:Throttle the processes programmatically by m8pple · · Score: 2, Informative
      Yeah, I though about mentioning it, but it seems like he's tied to NT. I'm using them for the same thing that I used to use the manual throttling for, and they are great, particularly when spawning lots of third party tools like compilers.

      AFAIK they work on any W2k or higher machine, but I could be wrong; I don't think I use any machines that aren't server (rather than pro) for my stuff.

    3. Re:Throttle the processes programmatically by borgboy · · Score: 2, Informative

      Yeah. According to the API docs, it works on W2k any edition, XP Pro and .Net Server. No go for NT, but I feel sorry for anyone still working in NT anyways.

      --
      meh.
  5. Re:ulimit? jeez by larien · · Score: 3, Informative
    Ulimit isn't the same thing; ulimit limits on total CPU time, not % CPU at any given time.

    Thus, if they run an app for some time (e.g. over a few days) they might run up 30 minutes total CPU time with no real problems. On the other hand, someone could start an app, peg it at 99% for 10 minutes and completely hammer the server.

    Operating systems like Solaris have add-ons to achieve system limits like CPU allocations to individual users/groups, but that is NOT ulimit.