bcooksley wrote:NSPluginViewer is probably Flash, which I disabled for virtually all sites except Youtube, but it still starts anyway.
No idea why KWin does ( which compositing effects do you have enabled? )

Yeah I have quite a lot of those...
Some I don't even use
Like Desktop cube, which I don't use at all. Or the duplicated: animated minimizing and magic lamp...
But I use present windows for alt-tab.. That might use up CPU...

i use 4.3 beta. the slowness is not related to firefox bing open (and i dont have nsplugin)

a recent example from a while ago

i power up the computer and start kde

i go to kopete settings (kopete icon in the tray - settings). it takes about 1 - 2 sec untill a blank grey window appears and then 1 - 2 sec more untill its contents appear

i close the window and try again. way faster but still a bit laggy

i go to keyboard language settings (tray too). again about 2 + 2 sec to draw first time and faster next time

i go to noatun settings (kde 3 application in the tray). about 1 - 2 sec to draw the window then contents appear near instantly (on the 1st time)

same delay (and faster on second time) when displaying some right click menus

ash wrote:i use 4.3 beta. the slowness is not related to firefox bing open (and i dont have nsplugin)

a recent example from a while ago

i power up the computer and start kde

i go to kopete settings (kopete icon in the tray - settings). it takes about 1 - 2 sec untill a blank grey window appears and then 1 - 2 sec more untill its contents appear

i close the window and try again. way faster but still a bit laggy

i go to keyboard language settings (tray too). again about 2 + 2 sec to draw first time and faster next time

i go to noatun settings (kde 3 application in the tray). about 1 - 2 sec to draw the window then contents appear near instantly (on the 1st time)

same delay (and faster on second time) when displaying some right click menus

I just went back to running KDE apps on fluxbox-- which is how I started with KDE-- and I'm happy once again. To see Dolphin (zoom!) zipping around, opening directories, and then (bang!) opening a konsole window in the same directory, and then (whoosh!) automatically following Dolphin as click though the directories, to finally see it doing this magic robustly reminds of why KDE applications are the best, and why I don't want to get involved with some lesser desktop environment. Now that I'm zooming along, happy as a clam (yeah, I know, clams don't really zoom, do they?) I can wait out the next step. You guys kind of screwed the pooch on the plasma thing, but I know you're going to come back strong like Rocky in the sequel, because you're not going to give up until you do. It's true what they say about you guys. You're cocky and reckless and you're not afraid to challenge your users. You make us suffer, but you suffer twice as much. I guess it's no secret that some were angry. Angry? Hell, I was livid! You created the best desktop environment ever, and at the moment of its perfection, you were already reaching for the handle to flush it down the ****. Sadly, not everyone has the vision to appreciate that kind of adventurous spirit, but I came to understand that this is where I belong.

It's also true what they say about KDE4. It sucks! It sucks hard... but someday it won't. I'll wait. Torvalds can go with gnome if he wants, but I know when they finally put me in that old folks' home, Gnome will probably be on every computer, and I'll use it then.

how is plasma related to slowness in applications ?

i killall'ed plasma-desktop and its faster now but still somewhat lags

ash wrote:i use 4.3 beta. the slowness is not related to firefox bing open (and i dont have nsplugin)

a recent example from a while ago

i power up the computer and start kde

i go to kopete settings (kopete icon in the tray - settings). it takes about 1 - 2 sec untill a blank grey window appears and then 1 - 2 sec more untill its contents appear

i close the window and try again. way faster but still a bit laggy

i go to keyboard language settings (tray too). again about 2 + 2 sec to draw first time and faster next time

i go to noatun settings (kde 3 application in the tray). about 1 - 2 sec to draw the window then contents appear near instantly (on the 1st time)

same delay (and faster on second time) when displaying some right click menus

I have to say that I don't have any of this problems. Apps open immediately. The only problem I have is that removing files takes too long. Especially when removing a directory with a lot of files.

I think that just after Beta 1 there were a couple of fixes regarding leaks (one being the kdeinit change made by Lubos Lunak), so Beta 2 may be better on memory usage.

For me, the most tangible manifestation of performance issues is when I try to view a video file with mplayer from the command line in KDE4, The display is halting, and I get an error message saying that "Your system is not fast enough to run this.",

but the usability issues are worse. I may be wrong about some of this, so let me know. It seems like I can no longer drag the panel from the top of the screen to the bottom of the screen, moving icons on the panel (if the panel wasn't locked) was just a simple drag and drop, but now it's two or three clicks to enable the setting change , and at least one click to disable the enabling.

Part of the reason why I'm being so annoying is that I've been using Slax lately, and I'm spending more time with the KDE3 desktop than ever before It's a revelation. Suddenly I understand why Desktop environments are supposed to be better than Window managers, and it's not about pretty icons, it's about being able to push around data as if it were a tangible object, and you can walk through walls. I'll never forget the moment when, totally by accident, I created a link on my desktop by dragging and dropping. I may have gasped. The link can be created in a moment and is completely functional . Drop something in here and it comes out there. This moment, which changed everything for me, was only about two weeks ago, and it made me see KDE4 with renewed alarm. I don't know to what extent this particular function is available in KDE4, but overall, that amazing fluidity seems greatly compromised.

The others don't get this right at all. Gnome doesn't ask me if I want to copy, move, or link a file when I drag and drop. It makes the decision for me. If it can move it, it'll move it, if it can't, it'll copy. And XFCE doesn't even have drag and drop at all.

Again, if anyone knows about me being wrong about the particulars, please correct me,

#lzfy

looks like your computer is more powerfull

here is my experience

moms shiny new core 2 duo 2 G ram mandriva - kde 4.2 flies (both with and without desktop fx)

my pentium 4 3.0 ghz 512 M ram archlinux - kde 4.2 and 4.3 are slow

my celeron 4 2.6 ghz 512 M ram archlinux - kde 4.2 and 4.3 are slow

my pentium 4 1.7 ghz 512 M ram archlinux - kde 4.2 used to be unacceptably slow. switched to kde 3.5 and now it beats the 3.0 ghz box

my pentium 3 1.0 ghz 256 M ram archlinux - kde 3.5 fast



#einar

i dont notice performance difference between 4.2.3 and 4.3 beta

the 'show paint' desktop effect points out inefficiencies in many places

bump !

i want to continue this discussion. especially with those who see whats going inside kde / kdelibs / qt

Actually, I said *after* beta 1, because I'm unsure of when those changes went in.

i'll try the latest builds ansd see

i do not really understand all your complains about kde4's bad performance, if you have an old pc use fluxbox or whatever, but in my opinion for modern hardware kde4 is the way to go.

i have a pc that flies with kde 3

i want it to be fast with kde 4

i consider a pentium 4 to be new enough computer

to me kde4.3beta1 runs faster, no problems with videos(mplayer from CL and dragon), the system sleep really fast to ram(less than 10segs) and wake up really fast to(less than 5segs). Only when you start kde the first time take a lot of time, but after that the sistem is fast.

To me looks like a lot of driver problems with nvidia/intel/ati, and thats not kde fault.