Originally posted by a user
View Post
Announcement
Collapse
No announcement yet.
Qt/GTK Speed On Unity/KDE/Xfce/LXDE/GNOME/Razor
Collapse
X
-
Originally posted by a user View Post1. the way it is done here it is not pointless at all
2. your article is WAY too outdated. gnome shell with mutter is using unredirected for fullscreen already since a long time. in this article it still talks about a mutter without that.
2. I know (I wrote that code after all) but this is irrelevant see 1.
Also unredirected windows should have more or less the same performance everywhere assuming no background work taking up resources.
Comment
-
Originally posted by e8hffff View PostWas the KDE system configured properly?
Comment
-
Originally posted by przemoli View PostIsn't QGears2 GLORIFIED "Do I have OpenGL AT ALL?" ???
Comment
-
Originally posted by drago01 View Post1. It isn't most of this benchmarks are not fullscreen and therefore the FPS they report might not be the FPS they actually draw on screen (please read the (non outdated) article).
the benchmarking was not done on my pc so all its results are useless.... no!
that's exactly what was benched: some specific circumstances. not being the scenario you desired to bench does not make it less usefull. you seem to expect a simple answer from a benchmark: what is the best xy?
sounds like the typical kids question, who has the bigger one?
the test provides some information about the influece of compositors in this test setup. it is neither ment as an all overall test, nor testing the impact of compositors during fullscreen etc.
i read the artical you mentioned. while makes some good technical points it simply doesn't fit to this test.
2. I know (I wrote that code after all) but this is irrelevant see 1.
when you bechmark a specifc scenario you get results that have to be interpred in context of it. doing a benchmark in another scenario than you wished doesn't make it useless or pointless.
Also unredirected windows should have more or less the same performance everywhere assuming no background work taking up resources.
Comment
Comment