On Fri, Sep 25, 2015 at 01:48:41PM -0400, Laine Stump wrote:
> On 09/25/2015 01:27 PM, Daniel P. Berrange wrote:
> >On Fri, Sep 25, 2015 at 05:22:30PM +0100, Daniel P. Berrange wrote:
> >>On Fri, Sep 25, 2015 at 11:13:52AM -0400, Laine Stump wrote:
> >>>There's a bit of background about this here:
On Fri, Sep 25, 2015 at 01:48:41PM -0400, Laine Stump wrote:
> On 09/25/2015 01:27 PM, Daniel P. Berrange wrote:
> >On Fri, Sep 25, 2015 at 05:22:30PM +0100, Daniel P. Berrange wrote:
> >>On Fri, Sep 25, 2015 at 11:13:52AM -0400, Laine Stump wrote:
> >>>There's a bit of background about this here:
There's a bit of background about this here:
https://www.redhat.com/archives/augeas-devel/2015-September/msg1.html
In short, virt-manager is calling the virInterface APIs and that ties
up a libvirt thread (and CPU core) for a very long time on hosts that
have a large number of interfaces.
On Fri, Sep 25, 2015 at 11:13:52AM -0400, Laine Stump wrote:
> There's a bit of background about this here:
>
> https://www.redhat.com/archives/augeas-devel/2015-September/msg1.html
>
> In short, virt-manager is calling the virInterface APIs and that ties
> up a libvirt thread (and CPU core)
On 09/25/2015 01:27 PM, Daniel P. Berrange wrote:
On Fri, Sep 25, 2015 at 05:22:30PM +0100, Daniel P. Berrange wrote:
On Fri, Sep 25, 2015 at 11:13:52AM -0400, Laine Stump wrote:
There's a bit of background about this here:
On 09/25/2015 01:27 PM, Daniel P. Berrange wrote:
So, I instrumented the netcf and augeas code to checking timings.
The aug_get calls time less than a millisecond, as do the various
other calls. I found the bulk of the time is actually coming from
the netcf function "get_augeas", which in
On Fri, Sep 25, 2015 at 05:22:30PM +0100, Daniel P. Berrange wrote:
> On Fri, Sep 25, 2015 at 11:13:52AM -0400, Laine Stump wrote:
> > There's a bit of background about this here:
> >
> > https://www.redhat.com/archives/augeas-devel/2015-September/msg1.html
> >
> > In short, virt-manager is
