| To: | pcp@xxxxxxxxxxx |
|---|---|
| Subject: | [Bug 1067] linux pmda does too much work for network.interface queries |
| From: | bugzilla-daemon@xxxxxxxxxxx |
| Date: | Tue, 05 May 2015 10:34:36 +0000 |
| Auto-submitted: | auto-generated |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <bug-1067-835@xxxxxxxxxxxxxxxx/bugzilla/> |
| References: | <bug-1067-835@xxxxxxxxxxxxxxxx/bugzilla/> |
|
Comment # 17
on bug 1067
from Michele Baldessari
(In reply to comment #16) > When the pcp client asks for {out,in}.{bytes,packets} only, we shouldn't > gather speed / duplex / etc. info in the first place. The "refresh" (= > preemptively load everything) mechanism is itself suspect. Fully agreed, but that is more of an architectural change for which I won't have time ATM. If you prefer I can split this specific "speed/duplex" issue into a separate BZ and we leave the more architectural one here. (The speed/timeout issue will still be present in Carlos' setup, although not when fetching {out,in}.{bytes,packets}) You are receiving this mail because:
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Bug 1067] linux pmda does too much work for network.interface queries, bugzilla-daemon |
|---|---|
| Next by Date: | [PATCH] configure: accept Open Build Service ps output, David Disseldorp |
| Previous by Thread: | [Bug 1067] linux pmda does too much work for network.interface queries, bugzilla-daemon |
| Next by Thread: | pcp updates: merge kenj (qa fixes and debian/systemctl), Mark Goodwin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |