You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Marketing wants to pump numbers of a GPU, so they tend to list an "effective clock frequency" that in the case of my 2080 Ti is the frequency you see and know of 1750 * 4 = 7000 MHz.
A fancy large number, but doesn't tell exactly and at a glance what the hardware is doing.
Describe the solution you'd like
A text field in the settings of btop like where you can currently input a GPU name, but you can type a multiplier or divider plus a number to have the displayed frequency correct without the "marketing" of it.
If there are other affected GPUs, this may also work in reverse to correct measurements rather than JUST Nvidia cards.
Describe alternatives you've considered
I had a look if this number can be tweaked elsewhere globally, and it does seem to be an annoyance on Windows too, but it comes from Nvidia's closed source driver, and changing that proprietary driver is not easy.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Marketing wants to pump numbers of a GPU, so they tend to list an "effective clock frequency" that in the case of my 2080 Ti is the frequency you see and know of 1750 * 4 = 7000 MHz.
A fancy large number, but doesn't tell exactly and at a glance what the hardware is doing.
Describe the solution you'd like
A text field in the settings of btop like where you can currently input a GPU name, but you can type a multiplier or divider plus a number to have the displayed frequency correct without the "marketing" of it.
If there are other affected GPUs, this may also work in reverse to correct measurements rather than JUST Nvidia cards.
Describe alternatives you've considered
I had a look if this number can be tweaked elsewhere globally, and it does seem to be an annoyance on Windows too, but it comes from Nvidia's closed source driver, and changing that proprietary driver is not easy.
The text was updated successfully, but these errors were encountered: