On 09/05/2015 05: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?
Yes and no. I have a similar configuration - Dell Optiplex - but with only 2G at the moment since other people needed those memory sticks .. <sigh>. Even so, with a FF process of nearly 100 tabs, right now (doing some research & testing), 80% memory consumes, 20% swap consumed, load average just over 1, swaping between any of the 4 full screen apps (Thunderbird, firefox, konsole with 6 tabs, konq if file mode with 4 main tabs and 6 tabs open on PDFs related to above mentioned research) i'm getting instantaneous response when switching. Tnis 'write' window opened instantnly. So what about starting other things? I click on games/patience. Oh, a delay, or at least its longer that switching between established tasks. about 1/8th of a second. Yes some thing like yast/software-install take time to come up, but for good reasons. You can see that more clearly doing command line zypper equivalent. The checking of the repositories so as to ensure integrity. And yes, running 'zypper up' slows things down, but so what? Coffee Time! So I think *you* have a problem. I can think of many things it MIGHT be, but the description you give isn't adequate. =================================================================== All that being said .... A phenomena I've seem is that with GUI systems there is always more 'eye candy' or under the hood stuff going on to soak up the additional processing power. According to Intel at the time, the processor of the original PC (or was it the AT) back at the start of the 1980s was about as powerful as a PDP-11. At that time I was working in a UNIX development shop and we were using a PDP-11 with 4 Meg of memory and a single drive. It was supporting about 40 developers. No gui then. All just command line. Mostly we were doing editing and compiling, but there was a good bit of emailing and the corresponding UUCP to support that. So how much more powerful are today's Intel/AMD processors in our desktops? Well, yes, a lot of the power is soaked up by the system. File systems are more complex than the original V7FS, take more calculation doing b-tree balancing. Virtual memory is more complex, more CPU intensive than a simple roll-in/roll-out. One can most clearly see the phenomena with MS-Windows where each release of Windows was there for each step forward in hardware, but the system never seemed to run any faster. Now, compare this to a non-GUI version of UNIX running on a IBM mainframe. I had this demo'd to me. Shell script to recompile the whole kernel tree. Enter command from the CLI. Hit enter. Command prompt comes back .. almost immediately. No perceivable delay. (Thank you Jeff Colyier for this) ========================================================== So I think YOU have a specific problems with your system. Perhaps one day i'll load up this Optiplex to 8G or 16G <drool>. Who knows what the Closet of Anxieties might produce? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org