status-interval not respected

[akiross]

So, after installing the plugin I noticed that my status bar was updated too frequently. Apparently, the presence of tmux-cpu influences the update and status-interval is ignored.

For example, if I set

tmux set -g status-right "%H:%M:%S"
tmux set -g status-interval 5

I can see the seconds updated every 5 seconds. On the other hand, if I add the tmux_cpu plugin:

tmux set -g status-right "%H:%M:%S #(/path/to/plugin/scripts/cpu_percentage.sh)"
tmux set -g status-interval 5

I will see the seconds and the CPU percentage updated almost every second, disregarding the value of status-interval. I think status-interval should be taken into account, and I see this behaviour as buggy.

I can help with the debug, but not being familiar with tmux-plugins in any way I don't know where to start.

[ctjhoa]

I'm not sure if this is something related to tmux-cpu or if this is something related to tpm or tmux in general.
Have you try the same thing with tmux-plugins/tmux-battery?

[ctjhoa]

ctjhoa@cl-mackbook ~ % time .tmux/plugins/tmux-cpu/scripts/cpu_percentage.sh
  8.3%
.tmux/plugins/tmux-cpu/scripts/cpu_percentage.sh  0.00s user 0.00s system 0% cpu 1.007 total

As you can see get cpu percentage is very slow because you can only get CPU from a time frame of 1 second (thanks to iostat). So maybe it have impact on the status-interval

[ctjhoa]

In theory, it should be something like this:

     0                  1                                                              5                6                                                             10
   start-interval                                                                    start-interval
      |------------------------------------------------------------------------------->|------------------------------------------------------------------------------->|

 start-cpu           end-cpu                                                          start-cpu           end-cpu 
      |---------------->                                                               |---------------->

[akiross]

cpu_percentage.sh is slow here as well because it uses an interval of 1, but it can be omitted: iostat -c is sufficient to get an immediate CPU usage statistic, instead of iostat -c 1 2 as it is now in the script.

In fact, replacing iostat -c 1 2 with iostat -c in the cpu_percentage.sh, the issue appears to be fixed and start-interval is honoured.

With the battery plugin it appears not to have this issue, at least using battery_remain.sh... Not knowing how tmux-plugins is implemented, I can't tell, but I think it's something structural causing this issue (i.e. in tpm).

EDIT: just to clarify, I'm on linux.

[ctjhoa]

From linux iostat man page:

The first report generated by the iostat command provides statistics concerning the time since the system was booted

so I cannot use the first report

[ctjhoa]

Same from BSD iostat man page:

The first statistics that are printed are averaged over the system uptime.

[akiross]

Right... So, another way has to be found :)

[ncdc]

FYI with the iostat in sysstat-11.5.4-2.fc26.x86_64, you can do iostat -c -y 1 1 to get the current cpu utilization. The docs for -y: Omit first report with statistics since system boot, if displaying multiple records at given interval.. I also had to change it to tail -n 3 instead of 2, FWIW.

[BrainMaestro]

I have this issue as well, and I think it's related to tmux/tmux#797 (comment). Maybe, as a way to fix this, the status-interval is checked, and if that number of seconds since the last time have not passed, just return the last value to avoid a redraw. Not the nicest solution since we have to keep track of two variables between draws, but it should work

[lonix1]

Is this still an issue in the latest bits, and what is the current recommended workaround (OP was a few years ago).

[ctjhoa]

@lonix1 iostat versions are very different across OSes and even depending on the version used. If you really care about the update frequency of your status bar, an alternative could be to add an option to customize the command used to compute CPU.