[BUG] Not able to display more than 5 GPUs

[Hugo Cartigny]

Hey!

1. When opening the app, no GPU stat is displayed, I have to display them myself by pressing the 5-9 keys on my keyboard
2. I am not able to go beyond 5 GPUs since I lack keys haha
3. Is there a way to display them nicely so that they take less space? I don't need 75% of my screen for 5 curves + I want to be able to display the 8 ones at the same time on top of the detailed CPU usage. Ideally I would want 1/3 of the screen for the CPU and 2/3 for GPUs

Thanks for your amazing work!

[romner]

You should be able to go into options > cpu and change Cpu graph lower/upper to something like gpu-totals, or delete your existing config which should set it automatically. 5-0 keys are mostly for inspecting individual GPUs in detail, which I assumed wouldn't really be needed for a system with >6 GPUs.

I'll make all of this more intuitive and probably add some bigger panels and that'd replace btop's existing mem net and proc eventually, but for now this is what works. I'd also be very interested if the CPU panel UI looks fine with this many GPUs, so please post a screenshot if you can.

[Hugo Cartigny]

@romner-set When selecting an option for "cpu-lower" I get this error when iterating through the list of possible values:

And now I cannot start btop anymore, I have to clear the config file.

I would like to be able to see the activity for each of the 8 GPUs though. They just don't have to take that much space

With 1 GPU and all CPUS it looks like this:

On 256 cores it looks awful tho

[romner]

@BlueskyFR please compile with DEBUG=1, run it like this and screenshot the output when the error occurs:

gdb bin/btop -ex run -ex backtrace -ex 'set confirm off' -ex quit

It's way more useful than one error message.

[Hugo Cartigny]

Here it is, still the same message:
(and I can't install the requested packages from the screenshot btw)

[Hugo Cartigny]

Hey, any news on your side?

[romner]

Sorry, I wanted to look into this before replying but I've been a bit busy the past few weeks so I didn't really have the opportunity. Currently the gpu-totals graph gets split up by the number of GPUs the system has, and I think it just can't handle this many...

Without a proper backtrace I have to either guess where the error occurs or have you test a bunch of different versions of the code, which isn't great. I've been working on adding an enable_gpu option to replace the current system where it only shows GPU usage if you have a GPU-related graph enabled, which should at least give you an overview of all the GPUs once it's done. Other than that I'll probably have to put this on hold for the time being, sorry.

[Hugo Cartigny]

Sorry, I wanted to look into this before replying but I've been a bit busy the past few weeks so I didn't really have the opportunity. Currently the gpu-totals graph gets split up by the number of GPUs the system has, and I think it just can't handle this many...

Without a proper backtrace I have to either guess where the error occurs or have you test a bunch of different versions of the code, which isn't great. I've been working on adding an enable_gpu option to replace the current system where it only shows GPU usage if you have a GPU-related graph enabled, which should at least give you an overview of all the GPUs once it's done. Other than that I'll probably have to put this on hold for the time being, sorry.

I can give some backtrack if you want

[romner]

Your gdb doesn't work properly, and it won't unless you install the packages it tells you. If you have another way to get a backtrace with the error's line number, feel free to post it.