On 09/05/2015 11:53 AM, Bjarne Örn Hansen wrote:
The past development of KDE gives me the notion of it being slow.
When I work in it and shift to a different application, the keyboard input is non responsive for up-to several seconds. I can hammer on the keyboard, and when the keys appear, there is lost keyboard input. Even if I merely hammer one key. My system is 4-cores, 3.5GHz, 16Gb system. Free shows me, there is amble memory left like 80%, and no swap usage.
Prior I have had several "slow" motion experiences with KDE, but they have been mostly related to continuous "search" functions being implemented. Top does not show any such activity. CPU shows 1.7us activity, so not overloaded. In fact, about 5% CPU usage.
I am not just seeing this in SuSE, in Ubuntu at work as well. KDE appears to be going down some bad development path.
Anybody have an Idea what is going on?
I don't know, but it is common here as well. The search you mention, is especially annoying, because the only way to run a command (the alt-f2 dropdown thing) uses search; when you enter a command it starts populating the list, but since you, at that point, haven't selected anything, the <enter> goes to waste and it doesn't do anything. I am too fast for it. I bet everyone is. I don't see why people use that or make it that way. It goes against anything that is natural. However, as a test here, whenever I alt-tab to KWrite, no input is ever lost. But, compared to Windows, there is definitely a sense of delay everywhere. Even the mouse/text cursor blink (text cursor blink) is too slow. You select a position in some text, and then you wonder if it will ever start blinking again. They should shave a few ms off, maybe like 20% less time for each interval. I never noticed before but I do now. I don't know what else, but especially the alt-f2 thing is extremely slow to come down, in the first place. Why should such a dialog take more than no-time to drop down?. Did they plan it that way? An artificial delay?. You start to wonder when you see the slow-blinking cursor. But I have no other issues with slow program response, other than that sometimes the simplest of things (like KWrite) take seconds to open, sometimes I wait 10 seconds for a KWrite to open. It's marvellous how ridiculous it is. It is the default editor, and it is unresponsive like that. Any default editor should open in a mere milisecond. I did a speed test: I press alt-f2 and start typing. The text came in this message compositor window of Thunderbird. The alt-f2 thing didn't start claiming the input soon enough. That's how slow it is. Now I am having to wait for my computer constantly. In Windows that was never the case (not for these things). I wish and wonder if there was an alternative to the alt-f2 thing that didn't use search and gave better error messages when a command was not found.... Search is not all bad but it shouldn't interfere. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org