Currently, if metrics shoot to some very high value, grid adjusts to it to address that spike, but then it stays that way, even if metric later drops and never grows that much again. Which basically can make the graph appear practically at zero all the time after that happens. It makes sense for grid to adjust to something lower as well, once all spikes are over. This auto-adjustment feature can be optional with some parameter which enables it.
There's already a modifier for that, from GALLIUM_HUD=help: 'd' activates dynamic Y axis readjustment to set the value of the Y axis to match the highest value still visible in the graph. (Maybe this should be the default though, at least for some graphs)
Thanks for the pointer! That helps indeed. I think for something like FPS metric, it can be a useful default. But then I guess you might want to have a negative modifier (counterpart to d).
System is crashing
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.