| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <BANLkTimCpH3Nn2XnOJUKnK=dMObj1r8KEg@mail.gmail.com> Date: Fri, 13 May 2011 09:39:08 +0200 From: Carl-Johan Kjellander <carl-johan@...rna.com> To: linux-kernel@...r.kernel.org Subject: Sched_autogroup and niced processes I've been running seti@...e niced to 19 in the background since 1999 without any problems. No noticeable effect even when playing a movie or a game. But since 2.6.38 the new fix-all-problems automatic grouping has been messing a bit with me. These are some timed compiles on my 8 cores. time make -j12 # with seti@...e running real 4m16.753s user 10m33.770s sys 1m39.710s time make -j12 # without seti@...e running real 2m12.480s user 10m11.580s sys 1m39.980s echo 0 > /proc/sys/kernel/sched_autogroup_enabled time make -j12 # no autogroup, seti@...e running again real 2m33.276s user 10m37.540s sys 1m43.190s All compiles already had all files cached in RAM. Now I can take the 10% performance hit, but not the 100% hit of running stuff super niced in the background. Processes niced to 19 should only use spare cycles and not take up half of the cores even with autogroup. I would really like to run autogroup since it is a neat idea, but it can't mess up running niced processes in the background which have been working fine for 12 years. /Carl-Johan Kjellander -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists