![]() | ||||||||||
Messages in this thread |
On January 11, 2002 11:24 am, you wrote: > On Wed, 9 Jan 2002, Ed Tomlinson wrote: > > Noticed something about tasks running with nice 19. They seem to > > always get 25-35% of the cpu. This happens with kernel compiles and > > some other benchmarking processes. If I kill the setiathome task, the > > other processes shoot up to 90% and above. > > why dont you run the setiathome task at nice +19? that way it'll share CPU > time with other niced processes. Setiathome _is_ running at nice +19... The H6 version cured the 2.4.17 boot problem here. Here are some numbers (H6) for you to consider: make bzImage with setiathome running nice +19 make bzImage 391.11s user 30.85s system 62% cpu 11:17.37 total make bzImage alone make bzImage 397.33s user 32.14s system 92% cpu 7:43.58 total Notice the large difference in run times... System is: UP K6-III 400, 512M Ed Tomlinson - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2005-03-22 12:15 [from the cache] ©2003-2008 | ||||||||||