Re: F36 Change: Plocate as the default locate implementation (Self-Contained Change proposal)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Zbigniew Jędrzejewski-Szmek wrote on Wed, Nov 24, 2021 at 07:58:47AM +0000:
> My understanding is that in order to minimize the overall energy consumption,
> the scheduler will try to maximize the cpu frequency and minimize the total
> time of computation… So a cpu scheduler will not help much here, as they
> will all schedule 100% of the cpu. AFAIK, there is no scheduler that
> allows saying "schedule this so that so that the fans don't go on".
> From the amount of complaints about loud fans, I think it would be a
> popular feature. (There is something similar with "lap protection", where
> heating is avoided if the laptop is detected as not-on-a-surface).

Right, from a total power consumption point of view this probably makes
sense, but it's not necessarily what people are after.


> Please try with the following file:
> 
> # /etc/systemd/system/plocate-updatedb.service.d/limits.conf
> [Service]
> CPUAccounting=yes
> CPUQuota=20%
> 
> (then 'sudo systemctl daemon-reload && sudo systemctl restart plocate-updatedb').
> I think this could work.

That's a nice one.

For my particular laptop, with governor=performance I'm cutting it too
close to fan being audible (and firefox etc also regularily kicks it
in), so I'm not surprised even with CPUQuota=20% it's enough to be
audible, albeit at a lower level than full throttle (something like +5°
instead of +10-15 from where core temp usually stands, that makes a
difference to fan RPM)

With governor=powersave though it's really worlds appart, no CPUQuota
immediately scales up to close to the max and heats just like
performance would but with this I barely see any difference from not
doing anything, cpufreq stays < 1GHz and heat stays way down. 

The consequence of that is it takes much longer to complete because the
clock is down: what previously normally took ~55s real for ~27s of CPU
time now takes 7m10 for 85s of CPU time -- but honestly I don't care how
long this takes if it's not noticeable, this is perfect. Thanks again!



Steinar would you consider adding this to the upstream service file?
(Zbigniew, does systemd just ignore the setting on systems where cpu
accounting has not been enabled? iirc some distros still have it off and
upstream might want to provide defaults that work everywhere)

I would have suggested also adding Nice=5 or something but I don't think
it's required with this.


Cheers,
-- 
Dominique
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux