[Digikam-devel] [Bug 185265] digikam constantly using some CPU in a poll loop due a timeout
Stefan Fleiter
stefan.fleiter at web.de
Fri Oct 16 20:18:05 BST 2009
https://bugs.kde.org/show_bug.cgi?id=185265
Stefan Fleiter <stefan.fleiter at web.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |stefan.fleiter at web.de
--- Comment #10 from Stefan Fleiter <stefan fleiter web de> 2009-10-16 21:17:55 ---
Still true for Version 1.0.0-beta5.
Amarok only uses some CPU while not playing audio after it has played audio
once.
This is tracked in phonon bug 204114.
But digikam is causes a lot of wakeups and thereby uses a lot of
cpu and power without playing audio once. So there does seem
to be another bug there.
This shortens battery lifetime for notebooks and netbooks considerably
and thus makes digikam not very well suited for mobile presentations
of photos.
See following powertop output:
PowerTOP 1.11 (C) 2007, 2008 Intel Corporation
Collecting data for 15 seconds
Cn Avg residency
C0 (cpu running) ( 1.5%)
polling 0.0ms ( 0.0%)
C1 mwait 0.0ms ( 0.0%)
C2 mwait 0.1ms ( 0.0%)
C4 mwait 6.4ms (98.5%)
P-states (frequencies)
2.21 Ghz 0.1%
2.21 Ghz 0.0%
1.60 Ghz 0.0%
1200 Mhz 0.1%
800 Mhz 99.8%
Wakeups-from-idle per second : 153.5 interval: 15.0s
no ACPI power usage estimate available
Top causes for wakeups:
46.1% (106.1) digikam : hrtimer_start_range_ns (hrtimer_wakeup)
24.1% ( 55.5) <interrupt> : extra timer interrupt
8.2% ( 18.8) <interrupt> : ahci
5.1% ( 11.8) <kernel core> : hrtimer_start_range_ns (tick_sched_timer)
4.3% ( 9.8) <interrupt> : ata_piix
3.5% ( 8.0) <kernel core> : usb_hcd_poll_rh_status (rh_timer_func)
2.8% ( 6.3) <kernel IPI> : Rescheduling interrupts
1.6% ( 3.7) <kernel core> : hrtimer_start (tick_sched_timer)
0.9% ( 2.0) <interrupt> : nvidia
0.5% ( 1.2) plasma-desktop : hrtimer_start_range_ns (hrtimer_wakeup)
0.4% ( 1.0) <kernel core> : add_timer (tg3_timer)
0.4% ( 1.0) <kernel core> : nv_kern_rc_timer (nv_kern_rc_timer)
0.2% ( 0.5) kwalletd : hrtimer_start_range_ns (hrtimer_wakeup)
0.2% ( 0.5) gpm : hrtimer_start_range_ns (hrtimer_wakeup)
0.2% ( 0.4) lancelot : hrtimer_start_range_ns (hrtimer_wakeup)
0.2% ( 0.4) hald-addon-stor : hrtimer_start_range_ns (hrtimer_wakeup)
0.2% ( 0.4) spamd : hrtimer_start_range_ns (hrtimer_wakeup)
0.1% ( 0.3) <kernel core> : neigh_periodic_timer (neigh_periodic_timer)
0.1% ( 0.3) konsole : neigh_periodic_timer (neigh_periodic_timer)
0.1% ( 0.2) konsole : hrtimer_start_range_ns (hrtimer_wakeup)
0.1% ( 0.2) dolphin : hrtimer_start_range_ns (hrtimer_wakeup)
0.1% ( 0.2) pdflush : wb_kupdate (wb_timer_fn)
0.1% ( 0.1) <kernel core> : inet_twdr_hangman (inet_twdr_hangman)
0.1% ( 0.1) hald-addon-stor : blk_add_timer (blk_rq_timed_out_timer)
0.1% ( 0.1) pdflush : add_timer (commit_timeout)
0.1% ( 0.1) ksoftirqd/0 : add_timer (sta_info_cleanup)
0.1% ( 0.1) kcryptd : blk_plug_device (blk_unplug_timeout)
0.1% ( 0.1) kded4 : hrtimer_start_range_ns (hrtimer_wakeup)
0.1% ( 0.1) krunner : hrtimer_start_range_ns (hrtimer_wakeup)
0.0% ( 0.1) <interrupt> : PS/2 keyboard/mouse/touchpad
0.0% ( 0.1) Xorg : hrtimer_start_range_ns (hrtimer_wakeup)
0.0% ( 0.1) bash : start_rt_bandwidth (sched_rt_period_timer)
0.0% ( 0.1) btrfs-submit-0 : worker_loop (process_timeout)
0.0% ( 0.1) events/0 : queue_delayed_work (delayed_work_timer_fn)
0.0% ( 0.1) kjournald2 : blk_add_timer (blk_rq_timed_out_timer)
0.0% ( 0.1) ssh-agent : hrtimer_start_range_ns (hrtimer_wakeup)
0.0% ( 0.1) NetworkManager : hrtimer_start_range_ns (hrtimer_wakeup)
0.0% ( 0.1) Xorg : add_timer (peer_check_expire)
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Digikam-devel
mailing list