poor system response after "nice'ing" a compute-bound process to 19

• Next message: William Montgomery: "Re: lowlatency-2.2.14-B1 + 2.2.14aa7 fixes crash, but..."
• Previous message: Mike A. Harris: "Re: Compiling kernel on different machine"
• In reply to: Patrick Spinler: "Re: What /proc should contain [was: /proc/driver/microcode]"
• Next in thread: Mark H. Wood: "Re: What /proc should contain [was: /proc/driver/microcode]"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

hi-

 I've got a compute-bound process (ok, its setiathome..) running on a
350mhz K6 under 2.2.14. In an attempt to recover some use of the
machine i've reniced the process to 19. System response,
mouse-movement, window-redraws are still very, very sluggish.

 Is this just the way it is? Even though a process has been niced to
19, does it still run its entire timeslice even though higher priority
processes are eligible to run?

 A buddy nextdoor with an old (slower) HP unix machine gets much better
system response with his setiathome niced to 19.

 just curious if this is the way its supposed to be-

Thanks

ron

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

• Next message: William Montgomery: "Re: lowlatency-2.2.14-B1 + 2.2.14aa7 fixes crash, but..."
• Previous message: Mike A. Harris: "Re: Compiling kernel on different machine"
• In reply to: Patrick Spinler: "Re: What /proc should contain [was: /proc/driver/microcode]"
• Next in thread: Mark H. Wood: "Re: What /proc should contain [was: /proc/driver/microcode]"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Tue Feb 29 2000 - 21:00:22 EST