KDE 4 Knetworkmager cpu% at ~37.5 - Mandriva

This is a discussion on KDE 4 Knetworkmager cpu% at ~37.5 - Mandriva ; Anyone running KDE 4. Would you please check cpu usage for knetworkmanager. Just loaded Kubuntu KDE 4 and Knetworkmager hovers around 37.4% cpu usage after about 3 minutes....

+ Reply to Thread
Results 1 to 6 of 6

Thread: KDE 4 Knetworkmager cpu% at ~37.5

  1. KDE 4 Knetworkmager cpu% at ~37.5

    Anyone running KDE 4.

    Would you please check cpu usage for knetworkmanager.

    Just loaded Kubuntu KDE 4 and Knetworkmager hovers around 37.4% cpu
    usage after about 3 minutes.


  2. Re: KDE 4 Knetworkmager cpu% at ~37.5

    Bit Twister wrote:

    > Anyone running KDE 4.
    >
    > Would you please check cpu usage for knetworkmanager.
    >
    > Just loaded Kubuntu KDE 4 and Knetworkmager hovers around 37.4% cpu
    > usage after about 3 minutes.


    Hey Bit Twister,

    KDE 4 on this Mdv 2008.1 box does not have that problem. net-applet appears
    in top every 5-10 secs as below.


    [test@sidney ~]$ top
    top - 08:27:26 up 20 days, 20:51, 1 user, load average: 0.14, 0.28, 0.16
    Tasks: 121 total, 1 running, 120 sleeping, 0 stopped, 0 zombie
    Cpu(s): 0.3%us, 0.2%sy, 0.0%ni, 99.5%id, 0.0%wa, 0.0%hi, 0.0%si,
    0.0%s
    Mem: 1028748k total, 995100k used, 33648k free, 93764k buffers
    Swap: 522072k total, 117156k used, 404916k free, 304728k cached

    PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
    7724 root 20 0 224m 131m 4116 S 0 13.1 83:02.60 X
    24614 test 20 0 531m 38m 16m S 0 3.8 0:01.63 knotify4
    24650 test 20 0 192m 40m 11m S 0 4.1 0:01.27 net_applet
    24689 test 20 0 235m 18m 13m S 0 1.8 0:00.72 konsole
    1 root 20 0 3792 516 484 S 0 0.1 0:07.06 init
    2 root 15 -5 0 0 0 S 0 0.0 0:00.00 kthreadd
    3 root RT -5 0 0 0 S 0 0.0 0:00.28 migration/0
    4 root 15 -5 0 0 0 S 0 0.0 0:14.40 ksoftirqd/0
    5 root RT -5 0 0 0 S 0 0.0 0:00.40 watchdog/0
    6 root RT -5 0 0 0 S 0 0.0 0:00.28 migration/1
    7 root 15 -5 0 0 0 S 0 0.0 1:57.07 ksoftirqd/1
    8 root RT -5 0 0 0 S 0 0.0 0:00.44 watchdog/1
    9 root 15 -5 0 0 0 S 0 0.0 0:05.16 events/0
    10 root 15 -5 0 0 0 S 0 0.0 0:04.61 events/1
    11 root 15 -5 0 0 0 S 0 0.0 0:00.00 khelper
    51 root 15 -5 0 0 0 S 0 0.0 0:05.36 kblockd/0
    52 root 15 -5 0 0 0 S 0 0.0 0:02.83 kblockd/1
    55 root 15 -5 0 0 0 S 0 0.0 0:00.00 kacpid
    56 root 15 -5 0 0 0 S 0 0.0 0:00.00 kacpi_notify
    154 root 15 -5 0 0 0 S 0 0.0 0:00.00 kseriod
    206 root 15 -5 0 0 0 S 0 0.0 1:16.99 kswapd0
    250 root 15 -5 0 0 0 S 0 0.0 0:00.00 aio/0
    251 root 15 -5 0 0 0 S 0 0.0 0:00.00 aio/1
    896 root 15 -5 0 0 0 S 0 0.0 0:00.00 kpsmoused
    914 root 15 -5 0 0 0 S 0 0.0 0:00.00 ksuspend_usbd
    915 root 15 -5 0 0 0 S 0 0.0 0:00.01 khubd
    938 root 15 -5 0 0 0 S 0 0.0 0:00.00 ata/0
    939 root 15 -5 0 0 0 S 0 0.0 0:00.00 ata/1
    940 root 15 -5 0 0 0 S 0 0.0 0:00.00 ata_aux
    [test@sidney ~]$

    --
    sid
    RLU 300284
    Mandriva 2008.1 X86_64
    2.6.24.3

  3. Re: KDE 4 Knetworkmager cpu% at ~37.5

    On Sun, 27 Apr 2008 07:35:10 GMT, sid wrote:

    > KDE 4 on this Mdv 2008.1 box does not have that problem.


    Thank you.

    I wanted to verify it was a Kubuntu distribution problem, not a KDE 4 problem.

    > net-applet appears in top every 5-10 secs as below.



    I did not notice net-applet so much as mdkapplet doing the same thing.

    PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
    4922 bittwist 20 0 29192 17m 10m S 0.3 2.0 1:00.91 mdkapplet

    I have been thinking about writing a bug report about that.

    Some programmer needs their butt kicked.
    Writes code with a default check time of 3 hours, yet it runs every
    5-10 seconds to see if it is time to check for updates is pretty abusive.

  4. Re: KDE 4 Knetworkmager cpu% at ~37.5

    Bit Twister wrote:


    >> KDE 4 on this Mdv 2008.1 box does not have that problem.

    >
    > Thank you.


    You're welcome

    > I wanted to verify it was a Kubuntu distribution problem, not a KDE 4
    > problem.


    Guess it is then

    >> net-applet appears in top every 5-10 secs as below.

    >
    >
    > I did not notice net-applet so much as mdkapplet doing the same thing.
    >
    > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
    > 4922 bittwist 20 0 29192 17m 10m S 0.3 2.0 1:00.91 mdkapplet


    I don't know about that as I never have mdkapplet running.

    > I have been thinking about writing a bug report about that.


    Is it really a bug?

    > Some programmer needs their butt kicked.
    > Writes code with a default check time of 3 hours, yet it runs every
    > 5-10 seconds to see if it is time to check for updates is pretty abusive.
    >


    So, not a bug but a feature
    What would you consider to be an appropriate default check time?
    --
    sid
    RLU 300284
    Mandriva 2008.1 X86_64
    2.6.24.3

  5. Re: KDE 4 Knetworkmager cpu% at ~37.5

    On Sun, 27 Apr 2008 13:30:32 GMT, sid wrote:
    > Bit Twister wrote:


    >> Some programmer needs their butt kicked.
    >> Writes code with a default check time of 3 hours, yet it runs every
    >> 5-10 seconds to see if it is time to check for updates is pretty abusive.
    >>

    >
    > So, not a bug but a feature
    > What would you consider to be an appropriate default check time?


    Hourly.
    That way, code runs only 3 times instead of 1,000+ times every 3 hours.

    mdkapplet install can drop a script into /etc/cron.hourly and decide if
    it is time to hit a mirror to see if there is anything to download.

    If user did not set even hour checks, code then submits it's self
    to run at a close enough time in cron.

    Rough example for that, can be seen in the half hour cron job script
    /etc/cron.d/php

  6. Re: KDE 4 Knetworkmager cpu% at ~37.5

    Bit Twister wrote:

    > On Sun, 27 Apr 2008 13:30:32 GMT, sid wrote:
    >> Bit Twister wrote:

    >
    >>> Some programmer needs their butt kicked.
    >>> Writes code with a default check time of 3 hours, yet it runs every
    >>> 5-10 seconds to see if it is time to check for updates is pretty
    >>> abusive.
    >>>

    >>
    >> So, not a bug but a feature
    >> What would you consider to be an appropriate default check time?

    >
    > Hourly.
    > That way, code runs only 3 times instead of 1,000+ times every 3 hours.
    >
    > mdkapplet install can drop a script into /etc/cron.hourly and decide if
    > it is time to hit a mirror to see if there is anything to download.
    >
    > [...]


    Well, your mileage may vary on what an appropriate default check time would
    be, but I know that on the Gentoo mirrors, they effectively _*ban*_ you
    from the mirrors for a given amount of time - I'm not sure exactly how long
    - if you check for updates more than five times per day - which is
    pointless anyway. ;-)

    --
    *Aragorn*
    (registered GNU/Linux user #223157)

+ Reply to Thread