-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider adding powerd #107
Comments
Here:
– note, that's not powerdxx for the installed manual page, but it is powerdxx for an online view e.g. https://www.freebsd.org/cgi/man.cgi?query=powerdxx(8) https://www.freshports.org/sysutils/powerdxx/
|
|
I have gathered all possible known to me FreeBSD power management options here for 2018: Maybe that will help you a little. Maybe since late 2018 (its 2021 now) some new options been introduced. I would also suggest a 'strange' but optimal thing:
The powerd increases clocks fast which makes sense on AC. |
Unfortunately temperature is not only one problem. Performance in gui applications is worse on freebsd than on linux. Even with fixed frequencies to turboboost mode on freebsd with dev.cpu.0.freq linux still smoother by default. Maybe it's drm-kmod issue. I've tried to configure xorg but it didn't help. Performance on Wayland is even worse. |
You can set optimal intervals in powerdxx with some flags as -p and -s. |
This comment has been minimized.
This comment has been minimized.
Its not about probing interval ... maybe I was not specific enough. With powerd when there is some load then its quite fast that the CPU clock will be rised to close to maximum speed. With powerdxx when there is some load then powerxx will increase the CPU speed but only a little - not close to maximum like powerd. Personally I myself use powerd (better for interactive use due to this 'faster' speed change) and with limit on the maximum speed. Currently my ThinkPad W520 has 4 cores with 2.3 GHz maximum speed + Turbo. I do not use Turbo at all and have limit of 1.8 GHz for maximum speed. This way even with 4 cores loaded at 100% I will not get that much high temperature and fan noise. I wanted to create a script that would kill powerd and start powerdxx when on work on battery is discovered and do the opposite when AC power is available, but for most of the time I work on AC anyway so I did not created it. If I would work on battery more then first I should replace my current battery as it has only 55% of its original capacity :)
Regards. |
Thanks :) I use suspend/resume a lot but often I run some backup jobs at night so my system remains powered on anyway :) |
Sounds to me like the authors of powerd and powerdxx should talk ;-) |
I have a portable heater in my bag ;~) |
A user on IRC noted that his notebook runs hotter on FreeBSD than on Linux and asked whether helloSystem manages P-States automatically.
We need to investigate this topic and possibly preinstall and preconfigure something like powerd.
https://www.freebsd.org/cgi/man.cgi?query=powerd
Also check
https://github.com/lonkamikaze/powerdxx
and see @vermaden's writeups on the subject
The text was updated successfully, but these errors were encountered: