trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: December 2011

Re: [trinity-devel] Slow TDE Exit Time

From: /dev/ammo42 <mickeytintincolle@...>
Date: Fri, 23 Dec 2011 03:29:52 +0100
On Thu, 22 Dec 2011 14:15:25 -0800 (PST)
Darrell Anderson <humanreadable@...> wrote:

> > > Regarding the fadeaway, long ago I wrote a bug report
> > to provide a
> > > KControl option to disable the fadeaway. The fadeaway
> > is too slow on
> > > older hardware. To me the fadeaway adds no meaningful
> > value but I'm
> > > not asking for a complete ripping. :) Lots of people
> > like that kind
> > > of eye candy, but we should have an option to disable
> > the effect for
> > > those who don't.
> > FYI even your K6-II could take benefit of MMX
> > optimizations.
> 
> One of my older machines is a 400 MHz K6-III+ with 256 MB of RAM, but
> you remember pretty close nonetheless. :)
I confused with the K6-II I used when I was a kid :)
> 
> The other clunker here is a 350 MHz PII. Well, I have a 486 still
> functioning, but nothing Linux related runs well on that box --- WFWG
> 3.11 with the Norton Desktop flies. :)
are you saying having tried a Linux distribution 15 years younger than
your 486... with busybox/uclibc or Slackware 4.0 the performance would
probably have been better ;)
> 
> I use those machines as a performance yardstick of sorts for older
> hardware. Most people today think a 1 GHz machine with 1 GB of RAM is
> old. Not in this house. :)
Not in mine either, such a machine is just "a little slow to use KDE4".
Especially with a Full HD panel and KWin effects automatically
activated ;)
Actually I still have a machine that I could use for KDE4/Trinity
optimisation (if I have the time to set up a cross-compiling
environment), it's not old (actually it's still in sale today) but has
a single-core non-x86 CPU and a very weak GPU which do a good job to
slaughter the Debian Squeeze's KDE4 performance.
> 
> Now, do you mean I need to recompile something to take advantage of
> MMX optimizations or are you referring to something in TDE code that
> should be tweaked with those optimizations?
It is not TDE code yet, but KDE4 code that could be imported into TDE
(or alternatively I could implement my own MMX intrisics code...)
> 
> Darrell
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> trinity-devel-unsubscribe@... For additional
> commands, e-mail: trinity-devel-help@... Read
> list messsages on the Web archive:
> http://trinity-devel.pearsoncomputing.net/ Please remember not to
> top-post:
> http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
>