Bug 215890
Summary: | High CPU load by gnome-vfs-daemon [dbus validation slow] | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Gian Paolo Mureddu <gmureddu> | ||||
Component: | dbus | Assignee: | David Zeuthen <davidz> | ||||
Status: | CLOSED WONTFIX | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 6 | CC: | alentejo2, bnocera, mclasen, thethirddoorontheleft, triage, vlada | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | bzcl34nup | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2008-05-06 16:50:19 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Gian Paolo Mureddu
2006-11-16 08:42:47 UTC
I ran this in sysprof, and it seems the validation of messages is really slow. The profile shows 70% of system cpu time spend reading the dbus messages. Created attachment 141647 [details]
profile for smb copy
This is a (large) sysprof profile for copying a large file. About 65% of the
system time is spent in _dbus_validate_body_with_reason. Although, as you can
see a large part of that (27% total system time) is actually ending up in
_dbus_real_assert.
*** Bug 212379 has been marked as a duplicate of this bug. *** I tried the dbus-1.0.0-2.fc6 build which has asserts and stuff disabled, and it seems a lot better. Are we gonna release that as an update? When i say better i mean the total cpu use is lower, and the copy is faster. However, dbus_validate_body_with_reason still takes 45% of the system time (although the used system time is less than before). I.E. There are still opportunities for optimization here. Alex, thanks for the confirmation. I wouldn't know how to run a profile to try and identify all the processes in volved. So this is a mixed situation? Part D-Bus and part gnome-vfs? No, its a dbus performance issue only. *** Bug 216478 has been marked as a duplicate of this bug. *** *** Bug 187592 has been marked as a duplicate of this bug. *** Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers This bug is open for a Fedora version that is no longer maintained and will not be fixed by Fedora. Therefore we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |