Recent renderer changes on v0.3 / debug - performance issues

Question

Recent renderer changes on v0.3 / debug - performance issues

Closed this issue 3 years ago · 17 comments

Recently there have been a lot of changes on v0.3 regarding rendering and timing.

This issue is meant to track any performance related problems happening now, especially non-smooth animations and gestures (low fps, dropped frames).

If you're experiencing any issues: Please check out the debug branch on pywm (v0.3 on newm), run newm for a very short time (maybe two or three low-performance animations, like 5 seconds in total) and upload the log file. Thanks!

@CRAG666 @DimitrisMilonopoulos

EDIT - Findings

The current timing method does not cope well with more than one monitor. In this case, many skipped frames and the like appear.

Answer 1 · 2022-02-12T15:40:27.000Z

@jbuchermn understrood :)

Answer 2 · 2022-02-12T15:55:42.000Z

I'm currently on the debug branch. Animations are clunky and slow on the second monitor on the main monitor they work fine

Answer 3 · 2022-02-12T15:57:53.000Z

@jbuchermn log https://drive.google.com/file/d/1ovHpkv5gnig5MlzmXWT3xTpuod1sCLcX/view?usp=sharing

Answer 4 · 2022-02-12T16:02:39.000Z

my current config https://github.com/CRAG666/dotfiles/blob/master/config/newm/configV3.py

Answer 5 · 2022-02-12T18:53:12.000Z

Thanks for the log, I'm studying it at the moment.

At first sight it looks like the two monitors perform quite differently (one looks okay, one looks very bad) - is this true, or do you see equally bad animations on both screens?

Answer 6 · 2022-02-12T20:39:34.000Z

Also.. I just realized, I made some git errors, so only now is damage branch up-to-date with v0.3. Would you mind trying again?

Answer 7 · 2022-02-12T23:21:50.000Z

@jbuchermn I just updated and if the error is still present, as I already mentioned, the error only occurs on the second monitor

Answer 8 · 2022-02-12T23:23:02.000Z

Can you also upload a new log?

Answer 9 · 2022-02-12T23:28:55.000Z

I'm a fool, compile v3 instead of debug. Debug works perfect.

Answer 10 · 2022-02-12T23:31:29.000Z

@jbuchermn the debug branch works very well, no latency or delays in the animations, everything goes very smoothly

Answer 11 · 2022-02-13T19:44:08.000Z

That‘s good to hear, although I'm not really confident this is consistent. For me, I do see occasional slow animations. Something about the timing is still off...

Answer 12 · 2022-02-13T23:19:50.000Z

@jbuchermn v3 already has the debug changes?

Answer 13 · 2022-02-13T23:25:50.000Z

If there is a delay I admit it but it is minimal very very minimal but if it improves it would be fine but for now I am satisfied

Answer 14 · 2022-02-15T22:24:05.000Z

@jbuchermn v3 already has the debug changes?

At the moment not. But I want to merge soon.

However, I just pushed major changes (again...) to debug. Can you try and see if there is lag or are any artifacts, ...? For me it appears to be more performant now.

Btw... renderer_mode does not need to be set anymore (also it has new values, wlr for passthrough and pywm for what was direct / indirect)

Answer 15 · 2022-02-16T17:16:31.000Z

thank, right now check the new changes and its configuration in nix

Answer 16 · 2022-02-16T23:22:55.000Z

@jbuchermn the debug branch works perfect. The experience is smoother now. I don't know if it has anything to do with it, but the representation of colors had a significant change. The colors are very vivid! this is amazing.

Answer 17 · 2022-02-17T07:55:38.000Z

That's great to hear :) I just merged debug into v0.3