00:22 <LaserEyess> luc4: you should ask your compositor's channel about that

00:31 <luc4> LaserEyess: the response I got was not completely clear, so I thought someone may be able to provide some hints here

00:35 <LaserEyess> ultimately, most performance related things are up to invidivual compositors to implement and maintain, so if things are slow for you on KDE plasma, only KDE plasma can help you fix them

00:35 <LaserEyess> (unless you're on nvidia, then no one can help you, not even nvidia)

00:36 <luc4> LaserEyess: I have nVidia, but it should only be used to offload on request, so I'm using Intel

00:44 <LaserEyess> sorry, I don't think I can help you either way, I was just trying to give the suggestion that you try KDE

00:44 <LaserEyess> if they can't help you I'm not sure anyone else can

00:46 <soreau> luc4: is it that you are seeing less fps in some frame counter or that it's causing an actual problem for you like stuttering?

02:26 <luc4> soreau: quality of animation is actually intolerable, while x11 is excellent

02:27 <luc4> soreau: so it is not just a number reported somewhere, it is an actually unacceptable behavior

02:28 <luc4> LaserEyess: as I said, no reasonable answer from KDE guys yet. This IRC channel has this topic: "discussion about the Wayland protocol and its implementations", so I think it is reasonable to look for answers here also.

02:29 <luc4> LaserEyess: if you don't know the answer, I'm not forcing you to answer of course.

02:34 <keyvan> Force. Lol

10:14 <maxzor> is there no egui-wayland integration yet?

10:16 <maxzor> sorry wrong channel *

10:52 <daniels> luc4: I would strongly suspect that it’s a multi-GPU issue, and that if NV were disabled completely then everything would work fine. have you provided the Plasma/KWin people with logs?

10:54 <luc4> daniels: this is a prime setup, so I don't think dgpu should be used unless specified, but I could try to disable it somehow. I reported an issdaniels: this is a prime setup, so I don't think dgpu should be used unless specified, but I could try to disable it somehow. I reported an issue years ago. No answer whatsoever. I tried to ask other times, but no clear answer was provided except "driver issue", but without any evidence.ue

10:55 <luc4> ask other times, but no clear answer was provided except "driver issue", but without any evidence.

10:55 <luc4> *ops, sorry, wrong copy-paste

10:56 <daniels> yeah, the only way your performance could be ‘unacceptable’ is if it were constantly copying or synchronising … how have you configured Plasma to avoid NV?

10:57 <luc4> daniels: this is a prime setup. Running on nv requires explicit usage of prime-run or specific env variables.

10:57 <daniels> I see

10:57 <luc4> daniels: but there may be something going on behind the curtain anyway

10:58 <luc4> however, I noticed yesterday that animations on a secondary FHD screen where almost perfect

10:58 <luc4> so, moving the window on the built-in 4K display has low framerate, but moving the same window on the FHD display is perfect

10:59 <luc4> a good test would probably be to blacklist nVidia probably, maybe there is a non-destructive way of doing it

11:00 <daniels> I’m afraid I can’t give you much further pointers without knowing anything about KWin

11:00 <luc4> daniels: I perfectly understand. I was hoping someone had experience with it.

11:01 <daniels> I think they have their own IRC channel?

11:03 <luc4> daniels: of course, I tried there

11:03 <daniels> ah

11:04 <luc4> I'll try to blacklist nvidia and, in case, I'll give up once again

14:06 <zamundaaa> luc4: when did you ask, and on which channel (+server)?

14:07 <zamundaaa> KWin completely ignores the dGPU unless an external monitor is connected, and even then it'll only use it for copying the composited image to the output. I can also guarantee you that it's not using the NVidia GPU for compositing because that was never implemented in KWin

14:08 <zamundaaa> (NVidia for compositing + anything else for output)