Re: performance

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: performance
by Ben on Monday 26/Feb/2007, @13:21

And I thought I was pushing it with 800MHz+378MB ram.

What distro do you guys use? I'm on debian testing.

Related Links

·   Articles on Developer
·   Also by Ben
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: performance
by personmandude on Monday 26/Feb/2007, @16:22

Slackware all the way brotha
I'm using slackware 10.0 with a big mix of newer software, but I'm thinking of upgrading to 11.0 soon. It's compiled with GCC 3.4 as opposed to GCC 3.3, so it should be a wee bit faster....

Well yeah, at the beginning of the KDE 4 journey there was a lot of hype about how performance was going to be improved, etc...
I'm hoping that it actually wil :) :)

[ Reply To This | View ]

Re: performance
by superstoned on Tuesday 27/Feb/2007, @03:29

Well, in some area's, performance will be improved. I guess memory usage can be lower if you disable certain things like strigi's indexing daemon. In any case, you'll have more features for your memory, as Qt4 binaries use approx 20% less memory compared to the same Qt3 executable. And there are more opportunities to use hardware acceleration in KDE/Qt4, so painting might be faster, even on slower hardware without 3D hardware (even 2D could be used better ;-))

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"I don't sing in the shower... I play the piano though." -- David Faure
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.