Please sign in to comment.
Revert "Restore 1000hz tick configuration"
It seems that I miscalculated the impact of 1000hz by just measuring the time that timer interrupts consume from powertop. During a full kernel build, with 1000hz, the kernel consumes about 8% of total system resources, much more than the 4-5% that 250hz consumes. Also, on my personal and work laptops, the 1000hz tick consumes significantly more power than its 250hz counter part. Temperature-wise, my work E7450 idles at 50-51c with 1000hz while the 250hz kernel idled at 36-40c, a massive difference! Not to mention, estimated battery life increased from 3-4 hours on a full charge to 6-7. Until we can fix the tickless idle feature of MuQSS, lets keep MuQSS at 250hz. Or we can always switch back to CFS entirely, but that'll take more research, benchmarks, and other important measurements to decide. This reverts commit 42c120e.
- Loading branch information...
Showing with 12 additions and 12 deletions.