The claim US WEST is making, or made since I doubt they still believe it, is
that the software itself, in the process of all those fun FFT calculations,
was tying up the processor. We all know it only takes idle time, but when
you look at performance monitor in NT, all you see is that
I don't know if he was aware of this problem, but
finally I had to obey because he insisted that
his machine runs slower if mprime runs on it,
and that it doesn't matter if other users agree to let
me run mprime on their machines,
while he as the administrator forbids it.
I use teh script
Given two programs, one running at normal priority, the other at the
lowest possible priority (idle priority), the second program will get
around 1-2% of the CPU,
I noticed the same thing under Linux (with rc5des). Idle processes get a
few % cpu time even on perfectly busy systems.
You might
Morten Due Jorgensen wrote:
Given two programs, one running at normal priority, the other at the
lowest possible priority (idle priority), the second program will get
around 1-2% of the CPU,
I noticed the same thing under Linux (with rc5des). Idle processes get a
few % cpu time even on
Simon Burge writes:
You may want to try what I do with some of our machines - instead
of killing and restarting the program, send it a STOP or a CONT
signal (I assume Linux has these signals available, I'm a BSD and
SysV person).
Yes, Linux has them, being a mostly POSIX-compliant
