While power efficiency is fine for most use-cases, it can introduce latencies due to the fact that the CPU can be running at a low frequency to save power and also switching from a deep C state when idle to a higher C state when servicing an event can also increase on latencies.
In a somewhat contrived experiment, I rigged up an i7-3770 to collect latency timings of clock_nanosleep() wake-ups with timer event coalescing disabled (timer_slack set to zero) over 60 seconds across a range of CPU scheduler and governor settings on a 4.15 low-latency kernel. This can be achieved using stress-ng, for example:
sudo stress-ng --cyclic 1 --cyclic-dist 100 –cyclic-sleep=10000 --cpu 1 -l 0 -v \ --cyclic-policy rr --cyclic-method clock_ns --cpu 0 -t 60 --timer-slack 0
..the above runs a cyclic measurement collecting latency counts in 100ns buckets with a clock_nanosecond wakeup interval of 10,000 nanoseconds with zero % load CPU stressor and timer slack set to 0 nanoseconds. This dumps latency distribution stats that can be plotted to see where the modal latency points occur and the latency characteristics of the CPU scheduler.
I also used powerstat to measure the power consumed by the CPU package over a 60 second interval. Measurements for the Intel-Pstate CPU scheduler [performance, powersave] and the ACPI CPU scheduler (intel_pstate=disabled) [performance, powersave, conservative and ondemand] were taken for 1,000,000 down to 10,000 nanosecond timer delays.
1,000,000 nanosecond timer delays (1 millisecond)
The ACPI CPU scheduler in performance mode has the best latency distribution followed by the Intel-Pstate CPU scheduler also in performance mode.
100,000 nanosecond timer delays (100 microseconds)
10,000 nanosecond timer delays (10 microseconds)
In this scenario, the ACPI CPU scheduler in performance mode was consuming the most power and had the best latency distribution.
It is clear that the best latency responses occur when a CPU scheduler is running in performance mode and this consumes a little more power than other CPU scheduler modes. However, it is not clear which CPU scheduler (Intel-Pstate or ACPI) is best in specific use-cases.
The conclusion is rather obvious; but needs to be stated. For best low-latency response, set the CPU governor to the performance mode at the cost of higher power consumption. Depending on the use-case, the extra power cost is probably worth the improved latency response.
As mentioned earlier, this is a somewhat contrived experiment, only one CPU was being exercised with a predictable timer wakeup. A more interesting test would be with data handling, such as incoming packet handling over ethernet at different rates; I will probably experiment with that if and when I get more time. Since this was a synthetic test using stress-ng, it does not represent real world low-latency scenarios, however, it may be worth exploring CPU scheduler settings to tune a low-latency configuration rather than relying on the default CPU scheduler setting.