[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 234463] Very high CPU usage.
From:       Thomas Lübking  <thomas.luebking () gmail ! com>
Date:       2011-06-15 7:44:01
Message-ID: 20110615074401.B5CD08B15B () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=234463





--- Comment #116 from Thomas Lübking <thomas luebking gmail com>  2011-06-15 09:43:41 ---
http://www.nvidia.com/object/linux-display-ia32-275.09.07-driver.html

And YES: I can confirm some improvement as well.

The "benchmark" shows sane numbers after KDE startup, launching (kapplication?)
GUI processes slow down the "benchmark" (only) a little.

So launching kmail + akonadi + the latter ones many (semi-GUI) processes causes
_slight_ slowdowns, shutting down them (kquitapp kmail, akonatictl stop)
however "improves" (reverts) the situation, so the pixmap cache is apparently
kept clean.
This is also supported by the fact that while turning it off, the "bench"
performance and overall speed drops dramatically but turning it back on brings
the benchmark to the previous numbers "only".

So, for resizing windows it's pretty significant (read: "impressive")
It should also cover the "hang on activation from any kind of effect" issue.

QtWebKit still prefers the native graphicssystem, but that's maybe not even an
nvidia issue at all (unfortunately i've no qtwebkit benchmark to really test
its check performance)

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]