Originally posted by zoomblab
View Post
Announcement
Collapse
No announcement yet.
GNOME 3.34's Mutter Lowers Output Lag On X11 To Match Wayland Performance
Collapse
X
-
-
Canonical made the mistake to succumb to the Red Hat controlled ecosystem (gnome & friends). I kind of get the why. Up to today all attempts to challenge this by any distribution have failed. Canonical gave in to gain "points" in the enterprise crowd in which RH is deeply entrenched. I still think it was a wrong move. They had the opportunity to become the Apple analogous to the Microsoft of 00s. Now they became followers instead of leaders.
Leave a comment:
-
Originally posted by debianxfce View Post
KDE is not any better than gnome3. KDE is badly designed, never ready, buggy, slow, resource hog and difficult to use too. The best distributions use the Xfce desktop that is ready, stable, fast, light, easy to use and needs a very little maintenance.
- Likes 2
Leave a comment:
-
Originally posted by msotirovMan, it's such a shame that Canonical didn't end up going with KDE and investing their developer's time there instead of at Gnome.
Leave a comment:
-
Originally posted by 144Hz View Postmicrocode You misunderstood. Vanvugt is a special breed. He won’t do reviews or merges on other people’s work. He just do patches and often break protocol on commit messages, styles etc. That’s totally fine because Canonical also have other mutter developers who do reviews, merges and janitorial CI fixes. Canonical and GNOME is really kicking it. Words from Mark Shuttleworth is that the cooperation is very good.
Leave a comment:
-
Originally posted by treba View PostVanvugt has done some really great work to make GS better. Unfortunately he doesn't seem to coordinate very closely with the rest of the gnome community, unlike some other Canonical fellows. Therefore his work sometimes ends up not matching the direction of the rest of the project, taking longer to get reviewed or doesn't get merged at all.
Still I'm always happy when one of his MRs finally crosses the finish line
Leave a comment:
-
Originally posted by angrypie View PostWill it solve that weird half-second freeze when you press a "normal" key after a multimedia key?
Output lag and input lag are different problems. Yes it would be good to have solid measurements on both.
- Likes 1
Leave a comment:
-
Will it solve that weird half-second freeze when you press a "normal" key after a multimedia key?
- Likes 1
Leave a comment:
-
Originally posted by bearoso View Post
Same thing. Input lag, output lag, it’s the time between the input occurring and a reaction happening on the output, so both terms are fine.
This is is one of two of vanvugt’s long-standing patches to be committed in the last few days. Pretty soon we won’t need to patch Mutter to get the lag to an acceptable level.
Input lag is the time the input takes to get to the application.
output lag is the time the generated output takes to get from the application to screen.
Total latency is input lag+ output lag + application processing lag.
Rough eyeballing is total latency and a guess where the problem is.
Depending on what form of lag alter what area of code needs fixing. If the problem is output lag and you are attempting to fix input lag developer will never find the problem. Same with the reverse.
Last edited by oiaohm; 21 May 2019, 06:16 PM.
- Likes 8
Leave a comment:
-
Glad to see performance optimizations for X11 as it's not going anywhere.
- Likes 5
Leave a comment:
Leave a comment: