| 1 |
On Donnerstag, 13. Dezember 2007, Philip Webb wrote: |
| 2 |
> 071214 Shawn Haggett wrote: |
| 3 |
> >> CONFIG_HZ_100=y |
| 4 |
> >> # CONFIG_HZ_250 is not set |
| 5 |
> >> # CONFIG_HZ_300 is not set |
| 6 |
> >> # CONFIG_HZ_1000 is not set |
| 7 |
> >> CONFIG_HZ=100 |
| 8 |
> > |
| 9 |
> > Smaller numbers here actually mean less clock interrupts per second. |
| 10 |
> > ie the CPU doesn't have to spend as much time switching between |
| 11 |
> > processes, but also a process will have to wait longer |
| 12 |
> > if another is currently using the CPU. |
| 13 |
> > Higher numbers tend to be good for getting faster responses, |
| 14 |
> > since the process on average shouldn't have to wait as long |
| 15 |
> > to actually get back on the CPU. |
| 16 |
> > 1000Hz for a really low latency desktop machine. |
| 17 |
> |
| 18 |
> I don't play games, but I've long had my desktop box using HZ_1000 |
| 19 |
> & it has always been very responsive (now Intel Core 2 Duo, 2.6.23-r3). |
| 20 |
> That's certainly the first thing to try. |
| 21 |
|
| 22 |
|
| 23 |
I have the best results with 300Hz. With 1000Hz the kernel wastes to much time |
| 24 |
context switching. Compiling is slower, gaming FPS lower ... |
| 25 |
-- |
| 26 |
gentoo-user@g.o mailing list |
Archives