Bug 213050 - High CPU load due to KGet
Summary: High CPU load due to KGet
Status: RESOLVED DUPLICATE of bug 160227
Alias: None
Product: kget
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-04 10:02 UTC by Axel Braun
Modified: 2010-01-02 01:06 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Axel Braun 2009-11-04 10:02:33 UTC 
Version:           2.3.2 (using 4.3.2 (KDE 4.3.2) "release 5", KDE:43 / openSUSE_11.1)
Compiler:          gcc
OS:                Linux (i686) release 2.6.27.37-0.1-pae

I feel the CPU-load that KGet creates is quite high for a download in the background:

Tasks: 146 total,   3 running, 143 sleeping,   0 stopped,   0 zombie
Cpu(s): 28.2%us, 14.6%sy,  0.0%ni, 55.8%id,  0.0%wa,  0.3%hi,  1.0%si,  0.0%st
Mem:   1020472k total,   993064k used,    27408k free,     9252k buffers
Swap:  2104504k total,     7268k used,  2097236k free,   567496k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 3913 axel      20   0 96044  25m  20m R 19.9  2.6   1:21.61 kget
11333 axel      20   0 94088  39m 4588 S  8.6  4.0   0:35.36 kio_file
11586 axel      20   0 61064 9616 6428 R  7.3  0.9   0:31.92 kio_http
 3874 axel      20   0  318m  53m  34m S  3.3  5.3  25:59.08 plasma-desktop

....
Comment 1 Matthias Fuchs 2009-11-14 18:58:14 UTC 
I can not really comment on this, as these figures really depend on the computer you use.

Could you please try KGet from trunk (what is to become KDE 4.4) or wait for the first KDE 4.4 Betas/RCs and try it with those to see if the problem remains?
Comment 2 Dario Massarin 2009-12-28 23:17:46 UTC 
Axel, did you try kget recently from one of the KDE 4.4 Beta? And if not, could you?
Comment 3 Lukas Appelhans 2010-01-02 01:06:37 UTC 

*** This bug has been marked as a duplicate of bug 160227 ***