Recent Features
| |||||||||||||
Fast clocks on slow hardwareFast clocks on slow hardwarePosted Jun 23, 2005 19:29 UTC (Thu) by larryr (guest, #4030)In reply to: Fast clocks on slow hardware by utoddl Parent article: What to merge for 2.6.13?
I would be surprised if going from 100Hz to 1000Hz made the system more than 10% slower as far as total throughput. The main area where the change should be noticeable is improvement in interactive response. The scheduling in 2.6 is significantly different from 2.4, independent of the time slice value. Larry
(Log in to post comments)
Fast clocks on slow hardware Posted Jun 24, 2005 2:22 UTC (Fri) by giraffedata (subscriber, #1954) [Link] In fact, the only time I've ever heard anyone complain about the clock tick overhead is on systems where lots of Linux systems share the same CPU and are designed for most of those Linux systems to be idle most the time (the clock ticks even on an idle system).In this case, I'd bet money the myriad differences in the kernel between 2.4 and 2.6 all taken together have nothing to do with the slowdown. A whole lot of other software has changed here too. Remember that when CPUs were about 1000 times slower than this 200 MHz thing, Unix systems were already performing reasonably at 100 Hz. So processing 10 times as many ticks ought to be OK.
|
|||||||||||||