Bug 226502 - kwin slow with composite ON
Summary: kwin slow with composite ON
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-12 11:46 UTC by Alberto
Modified: 2011-12-22 10:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In: 4.8.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alberto 2010-02-12 11:46:46 UTC
Version:            (using KDE 4.4.0)
OS:                Linux
Installed from:    Ubuntu Packages

When I turn Kwin is slow, very slow.I have an ATI 4850 that is capable of displaying many more FPS per second in previous versions of KDE, but now everything is very slow.

I used the FPS meter and with only kopete, konqueror and dolphin display noticeable speed downturns, giving a maximum of 33, even down to 20 when using Alt Tab (Mode cover).It relamente insufferable.

Ubuntu 9.10 and I updated with the latest ATI drivers
Comment 1 Martin Flöser 2010-02-12 11:56:38 UTC
Is your "being slow" just based on the fact that the fps effect displays a lower number? If yes, that makes the report invalid. Based on the way fps effect works it causes constant repaints which are for normal usage of compositing not relevant. For kwin or any compositing system it's important to paint as less as possible. While 20 FPS is not much it is still sufficient for smooth animations.

As you reported several bugs during the last hour and all are related to the proprietary driver: might it be that the driver is buggy? Could you try to use the free one?
Comment 2 Alberto 2010-02-12 12:19:59 UTC
es, maybe the ati drivers are the culprit, I do not know, I'm not a programmer.I reported some problems that only happens to me with KDE kwin 4.4.0.but I'm tired of seeing in the last year and finally I've been reporting.

But hey, if you like, I do not report these problems, I stop using KDE and go back to windows ...It's easy to understand, report a problem that only happens in KDE4 me after suffering a year.

It goes slow, I need a notifier of FPS, I turned to give some data.
Comment 3 Thomas Lübking 2010-02-12 15:07:00 UTC
(In reply to comment #2)
> But hey, if you like, I do not report these problems, I stop using KDE and go
> back to windows
Sorry, I'm not impressed. Find a better threat.
Maybe ask ati to ship better drivers or you're gonna buy nVidia ;-P

Martins comment however stands right:
the kwin fps plugin is NOT (and not intended to be) like the "showfps" command in a random shooter, and a compositing manager does not work like such either.
If this is the only base for your objection, it's worthless.

Sorry to say, but this:
> I reported some problems that only happens to me with KDE kwin
> 4.4.0.but I'm tired of seeing in the last year and finally I've been reporting.
makes no sense, as 4.4.0 was JUST released.
You _cannot_ have seen the issue _only_ in 4.4.0 over the last year.

Now, iff it worked faster before (e.g. 4.3) and you did NOT change the kernel/driver as well you might want to:
a) test another decoration (see whether e.g. the oxygen deco activation animations or the tabbing causes this)
b) see whether some plugin triggers this, 
- starting out with the obvious: if _only_ coverflow is slow but the cube and other verterx transforming FX are fast it's likely in the coverflow effect
- otherwise disable _all_ plugins except coverflow and see if it runs fast, then figure the culprit in case

Finally you can google for "ati linux slow compositing", check the instructions against your current settings and test what works for you (and no: setting up your driver is out of KWin's and probably entire KDE's scope - sorry)
Comment 4 Martin Flöser 2011-01-22 09:17:48 UTC
is this still an issue with a more recent version of KDE (4.6) and a more recent version of the drivers (Mesa 7.10)?
Comment 5 Martin Flöser 2011-12-22 10:33:59 UTC
As of 4.8 we have included many performance improvements, so I consider this bug as fixed.