Bug 609228
Summary: | network interface functions cause very high CPU utilization in libvirtd | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Laine Stump <laine> |
Component: | augeas | Assignee: | David Lutterkort <lutter> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 6.0 | CC: | berrange, clalance, crobinso, hbrock, itamar, jforbes, laine, lutter, mjenner, moli, rwu, schwab, syeghiay, veillard, zamsden |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | augeas-0.7.2-2 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 600141 | Environment: | |
Last Closed: | 2010-11-10 19:54:55 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: | |||
Bug Depends On: | 600141 | ||
Bug Blocks: |
Description
Laine Stump
2010-06-29 17:25:08 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. This BZ has been added to track necessary changes to augeas and/or netcf to avoid unnecessary re-reading of unmodified config files, either by using inotify, or just by stat'ing each file before it is re-read to see if it's been modified. There is also some talk of improving the efficiency of the parsing, but nothing concrete there yet. I am working on avoiding all those reparses transparently in augeas - with that change, reparsing unmodified files will be avoided at the cost of doing stats on those files and some internal bookkeeping. Please see corresponding Fedora bug for progress: https://bugzilla.redhat.com/show_bug.cgi?id=600141#c7 Since basic smoke tests by Laine and Cole indicate that it does improve the situation dramatically and does not cause regressions, this should be fixed with augeas-0.7.2-2 *** Bug 609214 has been marked as a duplicate of this bug. *** hi, i'm not quite sure the reproduce steps, i did saw in augeas git, the aug_load changed to load only update/modify file, and here is my steps to verify the bug, software version, augeas-libs-0.7.2-2.el6.x86_64 augeas-0.7.2-2.el6.x86_64 libvirt-0.8.1-21.el6.x86_64 1, run the virt-manager with 2 network script available(eth0, eth1), 2, running virt-manager for a long time, like 3 hours, 3,top -p $libvirt_pid, 4,if the bug not resolve, then virt-manager will keep polling the network configuration, and augeas keep reparse all the network profile, then libvirtd will cause high cpu utilization,but actually in my test, i didn't see the cpu utilization grows obvious,is this means the bug get fixed, can someone help me to check if the steps is right or if i miss sth? + /* To avoid unnecessary loads of files, we reload an existing file in + * several steps: + * (1) mark all file nodes under /augeas/files as dirty (and only those) + * (2) process all files matched by a lens; we check (in + * transform_load) if the file has been modified. If it has, we + * reparse it. Either way, we clear the dirty flag. We also need to + * reread the file if part or all of it has been modified in the + * tree but not been saved yet + * (3) remove all files from the tree that still have a dirty entry + * under /augeas/files. Those files are not processed by any lens + * anymore + * (4) Remove entries from /augeas/files and /files that correspond + * to directories without any files of interest (In reply to comment #9) > hi, i'm not quite sure the reproduce steps, i did saw in augeas git, the > aug_load changed to load only update/modify file, and here is my steps to > verify the bug, Yes, those are the right steps to verify the bug - it's a little up to interpretation what constitutes 'high load'. Certainly, the 13-20% of CPU usage that was initially reported was unacceptable. I'd say if you see loads that are significantly lower than that, this should be considered fixed. according to comment9,10, in my test, after running virt-manager for several hours with on guest running and several guest shutoff, the load of libvirtd is just about 0.7~3%, which is lower than the initially reported value 13~20%, so the bug is fixed, Red Hat Enterprise Linux 6.0 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you. |