Package Details: linux-ck 4.11.12-1

Git Clone URL: https://aur.archlinux.org/linux-ck.git (read-only)
Package Base: linux-ck
Description: The Linux-ck kernel and modules with the ck2 patchset featuring MuQSS CPU scheduler v0.156
Upstream URL: https://wiki.archlinux.org/index.php/Linux-ck
Licenses: GPL2
Provides: linux-ck=4.11.12
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 364
Popularity: 2.767442
First Submitted: 2011-07-22 14:51
Last Updated: 2017-07-21 19:13

Latest Comments

Junio_Calu commented on 2017-07-16 11:37

About P6_NOPS, should I enable it?

graysky commented on 2017-07-13 22:34

@gnu - done, will be in the next update, thks

gnubeest commented on 2017-07-13 15:02

Just for the sake of pedantry, next release you may want to change the URL preceding _BFQ_enable_ to https://wiki.archlinux.org/index.php/Improving_performance#Tuning_IO_schedulers as the fragment in the original comment is dead and the linux-ck page links there now anyway.

r08 commented on 2017-07-11 20:35

@QuartzDragon
@artafinde
Thanks for the feedback. I guess I'm not the only one... Will test this using CONFIG_HZ_PERIODIC=y to see if I get the same latency issues..

artafinde commented on 2017-07-09 07:17

@QuartzDragon: I have similar behaviour with my laptop here (Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz). I was setting the tick to 1000Hz before MuQSS but on the first iterations of MuQSS I think it was better. Do you get same freezes with linux from core? Is it fixed if you compile your own -ARCH and set tick to 1000Hz?

QuartzDragon commented on 2017-07-08 22:38

When I change CONFIG_HZ to 1000, CONFIG_HZ_100_MUQSS seems to be automatically unset.

artafinde commented on 2017-07-08 08:57

MuQSS 0.150 reverted the Hz back to 100Hz and I think that's the recommended value from ck. @QuartzDragon, r08 do you change both the below:

CONFIG_HZ_100_MUQSS=y
CONFIG_HZ=100

graysky commented on 2017-07-08 07:37

@Quartz and r08 - Post to ck's blog?

QuartzDragon commented on 2017-07-08 06:54

In the past, I too had noticed weird stuttering using 100Hz, so now I always set it to 1000Hz. System is smooth. :)

r08 commented on 2017-07-07 10:51

Interesting how I noticed slow downs using the default MuQSS@100Hz while using Firefox and running Steam games like Team Fortress 2.
Setting it to 1000Hz fixed the latency issues I was having. Should 1000Hz tick be the recommended setting for a "normal desktop user?"
Running old Intel Core 2 T9500@2.60Ghz

All comments