Here is what I found in the 450 user guide
Interaction of Burst Allocation and Sustained Data Rate Settings
If the Burst Allocation is set to 1200 kb and the Sustained Data Rate is
set to 128 kbps, a
data burst of 1000kb is transmitted at full speed because the Burst
Allocation is set high enough. After the burst, the bucket
experiences a significant refill at the Sustained Data Rate. This
configuration uses the advantage of the
settable Burst Allocation.
If both the Burst Allocation and the Sustained Data Rate are set to 128
kb, a burst is limited to the Burst
Allocation value. This configuration does not take advantage of the
settable Burst Allocation.
If the Burst Allocation is set to 128 kb and the Sustained Data Rate is
set to 256 kbps, the actual rate will be
the burst allocation (but in kbps). As above, this configuration does
not take advantage of the settable Burst
Allocation.
On 4/26/2015 11:16 AM, Kurt Fankhauser wrote:
I'm measuring at the upstream router which is actually a Procera Box.
(not actually a rotuer) Customer called last night complaining speeds
were horrible....
Kurt Fankhauser
Wavelinc Communications
P.O. Box 126
Bucyrus, OH 44820
http://www.wavelinc.com <http://www.wavelinc.com/>
tel. 419-562-6405
fax. 419-617-0110
On Sun, Apr 26, 2015 at 12:01 PM, Ken Hohhof <[email protected]
<mailto:[email protected]>> wrote:
Sorry to answer a question with a question, but are you measuring
at the SM, or at some upstream router?
The reason I ask, is I have seen some CDN traffic that does not
seem to follow traditional TCP congestion control. It will send
at twice the rate limit, causing 50% packet loss to its own
traffic and everything else to that same subscriber. Evidently
some TCP geniuses have decided to use latency rather than packet
loss as the indicator of congestion, and that the objective is
goodput not throughput. Works for last mile technologies like T1
and DSL with big buffers at the head end of the fixed speed serial
connection, not so good with the type of rate limit queues we tend
to use unless we can provision the queues with big buffers.
Probably not your problem, but I thought I’d bring it up just in case.
*From:* Kurt Fankhauser <mailto:[email protected]>
*Sent:* Sunday, April 26, 2015 10:50 AM
*To:* [email protected] <mailto:[email protected]>
*Subject:* [AFMUG] 450SM sustain bucket throttle not working..
I have a 450 SM that is rate limited in the SM to 1500kbps
download on the sustain side. I noticed last night that this
customer was pulling a steady almost 3mbps download for several
hours on end. How is this possible? Is there a problem with 13.2
firmware? Its a 3.65ghz SM.
see attached.
Kurt Fankhauser
Wavelinc Communications
P.O. Box 126
Bucyrus, OH 44820
http://www.wavelinc.com <http://www.wavelinc.com/>
tel. 419-562-6405 <tel:419-562-6405>
fax. 419-617-0110 <tel:419-617-0110>
--
