trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: February 2012

Re: Re: [trinity-devel] Poll

From: Martin Gräßlin <mgraesslin@...>
Date: Mon, 13 Feb 2012 18:05:43 +0100
On Monday 13 February 2012 11:53:00 Kristopher John Gamrat wrote:
> On Monday 13 February 2012 07:23:37 am /dev/ammo42 wrote:
> > On Mon, 13 Feb 2012 01:10:14 -0500
> > 
> > Kristopher John Gamrat <chaotickjg@...> wrote:
> > > On Monday 13 February 2012 12:07:18 am /dev/ammo42 wrote:
> > > > On Sun, 12 Feb 2012 20:06:59 -0800 (PST)
> > > > 
> > > > Darrell Anderson <humanreadable@...> wrote:
> > > > > Of course, geeks and trolls believe that everybody should buy
> > > > > bleeding edge hardware with gobs of RAM and CPU cycles to waste
> > > > > and just STFU.
> > > > 
> > > > One not really needs to have a "bleeding edge hardware" to run KDE4.
> > > > Unless you consider an €250 (without taxes) ultra-low-end box from
> > > > 2004 being bleeding edge.
> > > 
> > > If the window manager overloads a 2.4ghz dual core CPU with 4GB RAM,
> > > I'd say one needs "bleeding edge" to run it ;-) (I can't say anything
> > > about post-4.6 releases of KDE, but even with just the panel and two
> > > Konqueror windows open, KWin from 4.6 would overload my CPU when I
> > > would push Alt+Tab, and it would take several minutes to actually
> > > switch the windows; of course, I don't know how well it would perform
> > > now on 4.7 or 4.8, I keep hearing it's been improving)
> > 
> > My €250 box didn't run KWin effects (you can disable them instantly
> > with Alt-Shift-F12, or go in the System Settings to disable them
> > permanently), anyway it couldn't given the old "Graphics My A**" it has.
> > The KWin performance improvements on 4.7/4.8 are real, at least on my
> > all-AMD laptop with FOSS drivers.
> 
> Mine didn't have the KWin effects on either, I don't care much for any
> eye-candyish stuff.
Just as a note: KWin effects have nothing to do with "eye-candy". That's a 
very often appearing misconception. One of the ways to speed up your desktop 
is btw enabling effects as that is what everybody in the area of "bringing 
content to the screen" is considering as a modern approach (c.f. Wayland).

What you experienced is a rare bug, we have never understood and have never 
been able to reproduce. Furthermore it did not happen when desktop effects are 
used.

Anyway the code path in question has been reworked in 4.8 and uses now evil 
technology coming from mobile devices ;-) It ss in general much faster and I 
have not heard of any issue in that regard anymore.

Cheers
Martin

Attachments: