VinzC wrote:There are plenty of such questions with GNU/Linux! And the answer would always be: «because I can!»
Gusar wrote:Which is a valid answer as such. But still, -j16 on a dual-core has no real value, it's ridiculous. And if this "miracle" patch only does something at a ridiculous setting, it's equally valid to question the "miracleness" (yes, that's a word!

) of it.
graysky wrote:This is what Con argued. Why optimize a kernel to perform at insane workloads when 99.99 % of the user don't use their machines as such.
Well, I really don't like percentages like this (i.e. what's this estimation based on?) but I agree with you: most GNU/Linux users won't probably load their system that much hence the impact of the patch is limited. But the main advantage is there's no longer a need to manually tweak performance using a command. It's handled automatically, which clueless users will probably appreciate.
OTOH -j16 was indeed for the sake of testing. Of course it makes no sense to raise that number that much. [I've compiled hugin and then I saw the effect: computer not responsive for a while, high latency, high I/O rate and much longer waits.] But instead of restoring -j3, I'll keep -j5 for a while and see.
Finally, even if this patch might happen to prove useless for a majority of users, it doubtlessly comes handy with Gentoo just because compiling is a common task. No need to renice, just compile as much as you want and watch. That's the point.