bpytop icon indicating copy to clipboard operation
bpytop copied to clipboard

[REQUEST] Exponentially change refresh rate

Open tom-doerr opened this issue 3 years ago • 3 comments

Is your feature request related to a problem? Please describe. I'm always frustrated when I'm using Bpytop to monitor CPU and Memory usage over longer periods of time. When I do this, I increase the refresh interval to 60s, which does exactly what I want. However it's really frustrating to have to hold down the plus key for 20 seconds until the interval is at 60 seconds. It takes 20 seconds for me to reach the interval, but for other people it might take around a minute, since by default the key press repeat default is much slower. I would also like to use bpytop to view the stats over a whole day, but didn't yet find the patience to hold down the plus key for long enough.

Describe the solution you'd like Increase the interval exponentially: 2s -> 4s -> 8s -> 16s -> 32s -> 64s -> ...

This would make it much easier to reach high values.

Same goes for decreasing the interval: 2s -> 1s -> 0.5s -> 0.25s -> 0.125s -> ...

I suspect that no one wants the change the interval from 2s to 2.1s or 1.9s.

Describe alternatives you've considered Taping the plus key down.

BTW: I would appreciate it if the fastest interval could be something like 0.01, that would sometimes come in handy.

tom-doerr avatar Jan 14 '21 20:01 tom-doerr

@tom-doerr Why not just change it from the options menu where you can type in any number you want? ESC -> OPTIONS -> SYSTEM -> Update ms or o -> SYSTEM -> Update ms And then just press Enter and type in a new value...

aristocratos avatar Jan 15 '21 14:01 aristocratos

Thanks, that already helps! Didn't know that was an option. However I still believe that exponentially changing the refresh rate is more useful for the users. If someone really wanted to change the refresh rate from 2s to 2.1s he/she could do it in the settings.

tom-doerr avatar Jan 15 '21 18:01 tom-doerr

@tom-doerr

However I still believe that exponentially changing the refresh rate is more useful for the users.

I'ts a bit more complex bit of coding than it might seem since I'm not using any library for the input handling but wrote my own. And haven't had any reason to keep track of previous keys before. So it becomes a lot of effort for functionality that is more of a convenience than a necessity.

Not saying it's a bad idea, but will not be a top priority either.

aristocratos avatar Jan 15 '21 23:01 aristocratos