search for: bottelneck

..., which appears to be down to the config retrieval step, so much so that we''ve needed to increase timeouts to avoid our Apache/Mongrel puppetmasterd solution from timing out the connection. I''ve done some basic profiling, using --summarize and --evaltrace, which shows that the bottelneck *appears* to be happening at the config retrieval level: (This is on our monitoring server) Time: Attachedstorage: 2.00 Class: 0.00 Collectd conf: 0.01 Config retrieval: 85.91 Cron: 0.00 Exec: 34.11 File: 35.56 Filebucket: 0.00...

Hi, i dont fully understand this sentence, could someone be so kind to expleain me it? Any router performing a shaping function should be the bottleneck on the link, and should be shaping slightly below the maximum available link bandwidth. This prevents queues from forming in other routers, affording maximum control of packet latency/deferral to the shaping device.