3 ms·

> echo hw.perfpolicy="auto" >> /etc/sysctl.conf if the above worked (I'm not a openbsd user really) then why would the author need to create the utility that c

• throwawayboise 5y ago
  From the author's project page, "This is mostly a playground project so I can experiment with CPU frequency scheduling" It seems one advantage is that it offers more control and settings for those who want it. E.g. options for: -d downstepfrequency sets the steps removed every cycle when decaying, default to 100 -i inertia sets the number of cycles after which the frequency will decay, 0 is the default -m maxfrequency sets the maximum frequency the CPU can reach in percent, 100% is default -l minfrequency sets the minimum frequency the CPU must be lowered to, 0% is default -r threshold sets the CPU usage in % that will trigger the frequency increase, 30% is the default -s stepfrequency sets the percent of frequency added every cycle when increasing, 10% is default -t timefreq sets the milliseconds between each poll, 300 is the default -T maxtemperature sets the temperature threshold under which the maximum frequency will be temporary lowered until the CPU cools down