BBlack has submitted this change and it was merged.

Change subject: r::c::perf: raise netdev_budget a bit
......................................................................


r::c::perf: raise netdev_budget a bit

Change-Id: I3692c55f8ce324edfc9eacee07e04cb3fc0af1c7
---
M modules/role/manifests/cache/perf.pp
1 file changed, 7 insertions(+), 0 deletions(-)

Approvals:
  BBlack: Verified; Looks good to me, approved



diff --git a/modules/role/manifests/cache/perf.pp 
b/modules/role/manifests/cache/perf.pp
index 1604c6d..4d6e622 100644
--- a/modules/role/manifests/cache/perf.pp
+++ b/modules/role/manifests/cache/perf.pp
@@ -93,6 +93,13 @@
             # will see drops in col 2 of /proc/net/softnet_stat
             'net.core.netdev_max_backlog'        => 60000,
 
+            # budget: Similar to the above, default 300, and is the #packets
+            # handled per NAPI polling cycle across all interfaces.  You can 
see
+            # effects of this being too low in col 3 of /proc/net/softnet_stat.
+            # Caches show some small numbers there, so, experimenting with
+            # raising this a bit for now
+            'net.core.netdev_budget'             => 1024,
+
             # Default:1 - setting this to zero defers timestamping until after
             # RPS.  It's more efficient this way, but timestamp doesn't account
             # for any tiny delays in queueing before RPS, which I don't think 
is

-- 
To view, visit https://gerrit.wikimedia.org/r/295543
To unsubscribe, visit https://gerrit.wikimedia.org/r/settings

Gerrit-MessageType: merged
Gerrit-Change-Id: I3692c55f8ce324edfc9eacee07e04cb3fc0af1c7
Gerrit-PatchSet: 4
Gerrit-Project: operations/puppet
Gerrit-Branch: production
Gerrit-Owner: BBlack <[email protected]>
Gerrit-Reviewer: BBlack <[email protected]>
Gerrit-Reviewer: Ema <[email protected]>
Gerrit-Reviewer: jenkins-bot <>

_______________________________________________
MediaWiki-commits mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/mediawiki-commits

Reply via email to