Jeremy_Rand_Talos_ has quit [Remote host closed the connection]
Jeremy_Rand_Talos_ has joined #dri-devel
clamor has quit [Ping timeout: 480 seconds]
clamor has joined #dri-devel
davispuh has joined #dri-devel
YuGiOhJCJ has quit []
MrCooper has quit [Remote host closed the connection]
MrCooper has joined #dri-devel
bonzini has joined #dri-devel
kts has quit [Ping timeout: 480 seconds]
Jeremy_Rand_Talos__ has joined #dri-devel
rasterman has quit [Quit: Gettin' stinky!]
Jeremy_Rand_Talos_ has quit [Remote host closed the connection]
kts has joined #dri-devel
Spino has joined #dri-devel
nashpa has joined #dri-devel
dliviu has quit [Ping timeout: 480 seconds]
<Venemo>
jadahl: it looks like gnome-shell uses an excessive amount of VRAM. is this a known bug, or should I open a new issue about it?
<Venemo>
jadahl: around 700 MB, which is pretty significant on older GPUs that don't have a ton of VRAM
jsa1 has quit [Ping timeout: 480 seconds]
<emersion>
do you have a lot of non-GPU-accelerated clients running?
<emersion>
the compositor is responsible for uploading buffers to the GPU for these clients
jsa1 has joined #dri-devel
<Venemo>
emersion: it doesn't matter, it's the same even with nothing else running other than the desktop
<emersion>
700 MB doesn't seem *too* crazy. as a reference, sway (a minmal compositor) uses 250MB with a few shm clients
<emersion>
mutter probably needs to keep more buffers around for all of the fancy effects, views and widgets
<Venemo>
the issue is that it uses up 30-50% of all available VRAM on older GPUs, not leaving much for games
<emersion>
(the shell runs in the same process)
<Venemo>
at the moment I don't know if mutter alone is to blame or if it's due to missing modifiers support and/or poor choice of tiling formats in Mesa
<emersion>
if mutter uses triple buffering, that would also increase VRAM usage
<Venemo>
well, I'd like to understand what's happening and see if there is something we can do about it
haaninjo has quit [Ping timeout: 480 seconds]
Kayden has quit [Quit: Leaving]
Kayden has joined #dri-devel
MrCooper has quit [Remote host closed the connection]
Spino has quit [Remote host closed the connection]
kts has quit [Quit: Leaving]
kts has joined #dri-devel
bonzini has quit [Ping timeout: 480 seconds]
oeuaoeuoeu[m] has joined #dri-devel
immibis has joined #dri-devel
anholt has quit [Ping timeout: 480 seconds]
haaninjo has joined #dri-devel
sima has joined #dri-devel
<karolherbst>
Venemo: maybe it's mostly gtk4 using accelerated UI for everything and creating a lot of GL or Vk contexts is also allocating a lot of VRAAM?
<karolherbst>
"nvtop" might be able to tell as well
<Venemo>
karolherbst: I had thought that gnome-shell doesn't use gtk4
<Venemo>
or gtk at all
<karolherbst>
well other apps part of gnome might
<karolherbst>
like gnome-software running in the background also uses VRAM
<karolherbst>
anyway, nvtop might help
<Venemo>
but there are no apps in the background, just the shell
<Venemo>
if there were umr would tell me
haaninjo has quit [Ping timeout: 480 seconds]
nerdopolis has joined #dri-devel
oneforall2 has quit [Quit: Leaving]
oneforall2 has joined #dri-devel
jsa2 has joined #dri-devel
jsa1 has quit [Ping timeout: 480 seconds]
<emersion>
the shell doesn't use gtk
testaccount has joined #dri-devel
nchery has quit [Remote host closed the connection]
nchery has joined #dri-devel
testaccount has quit []
haaninjo has joined #dri-devel
iive has joined #dri-devel
JTL2 has quit []
JTL has joined #dri-devel
kts has quit [Quit: Leaving]
lassebq has joined #dri-devel
lassebq has quit [Quit: lassebq]
lassebq has joined #dri-devel
clamor has quit [Ping timeout: 480 seconds]
clamor has joined #dri-devel
anholt has joined #dri-devel
jsa2 has quit [Ping timeout: 480 seconds]
<jadahl>
Venemo: there should be one gl texture per shm client, and 2 to 4 fullscreen textures for each screen, and things like text glyph cache, some cached flattened widgets etc, but shouldn't be much more than that I think
<jadahl>
not sure what vram measurements tools there are to debug things
anholt has quit [Ping timeout: 480 seconds]
<jadahl>
unfortunately here intel_gpu_top says gnome-shell uses 0 in memory
<zmike>
nvtop?
anholt has joined #dri-devel
<jadahl>
that one does show indeed show almost 700
<jadahl>
seems it shows memory owned by clients too though, not sure
<jadahl>
opening some windows (vulkan client) makes the memory increase, then closing them makes it go down.
<jadahl>
we don't create any additional textures for client windows
<jadahl>
unless its shm clients
coldfeet has joined #dri-devel
lassebq has quit [Quit: lassebq]
lassebq has joined #dri-devel
jsa1 has joined #dri-devel
lassebq has quit [Quit: lassebq]
clamor has quit [Read error: Connection reset by peer]
<Venemo>
jadahl: interesting. I used umr for that on an amd gpu. there is an option to dig up more info on it if you're interested
<emersion>
i'd ne interested in learning how to dig into this too
sima has quit [Ping timeout: 480 seconds]
<Venemo>
launch the compositor with the AMD_DEBUG=extra_md / RADV_DEBUG=extra_md environment variable (the former for radeonsi, the latter for radv). then you're going to need the latest version of umr from git: https://gitlab.freedesktop.org/tomstdenis/umr because it got some recent bug fixes for parsing the info from the kernel. launch it with sudo umr --gui -> then on the GUI click on the tab corresponding to your GPU, click memory use and there is
<Venemo>
going to be a tree map with info on each BO
<emersion>
nice, will try when I'm back from XDC
<Venemo>
we can take a look at it together at XDC
<emersion>
tgat would be great! unfortunately except my laptop is not
<emersion>
amd
<Venemo>
well, then I can show it to you on my laptop
<emersion>
... early enter, sorry
<emersion>
yeah, sounds like that would be useful :)
<Venemo>
I haven't digged into it more than just looking at the overall vram amount used. it seems to depend on the screen resolution as well. when only a single display is plugged in and set to 1080p the default use goes down to around 300 MiB
<jadahl>
Venemo: unfortunately I don't have any amd hw
<Venemo>
jadahl: are you coming to XDC?
<jadahl>
no :/
feaneron has joined #dri-devel
<Venemo>
ah. I would have offered to just give you a gpu