Can any experienced mikrotik user give me an examle of using 16M download 1M upload internet line sample configuration for 80 user with queue,burst, threshold, burst time ?

I would love to see one script/tutorial for that too.

cheers

I learned it via trial and error. Wiki helps with the basics but the actual results are hard to "read". Best way to setup standards for your system is for you to set it up and then drive it. If you are running a ISP you'll need to remain focused on the customers perception as you fine tune all. The customers perception is also distorted via the competitions smoke and mirrors advertising. Bottom line line is the customers ability to run Netflix and/or any other like program. If it buffers they will see that as poor ISP performance.

Here is a note I wrote concerning what I learned;

Max Limit: this is the max. up & down load allowed when the burst settings are not managing the bandwidth.

Burst Limit; this setting is the maximum allowed burst limit. Note that the actual available bandwidth from the Access Point can be lower than this setting but this limit will effect the overall "time" a burst is allowed from the Access Point.

Burst Threshold: this is a point that allows or refuses burst. If the AVERAGE demand for bandwidth is below this number the Burst will NOT engage. Burst will disengage, as set for time/limits, when this number is reached.

Burst Time: Is NOT the actual time a burst is allowed. The actual time is calculated; Burst Time * Burst Threshold / Burst
Limit. Note that the actual bandwidth available at the time of the "Burst" is used to calculate the time the burst actually stays engaged. 80 * 2 = 160 divided by 8 = 20 seconds of allowed burst. If any of the values are changed the allowed burst time is also changed.



Notes;

- Speedtest.net needs a minimum amount of "burst time" for the test to record the "actual" bandwidth results at that time tested. I think our target time to program our queues to is 20 seconds. This allows speedtest.net to display to our customers a recorded value that represents our sales practices.

- Burst Threshold can be programmed to effectively reduce BURST's to our Access Points. Not sure how we can identify the proper Burst Threshold setting since this value directly effects the burst time.

- using a simple queue on a DHCP Server with multiple customers is NOT manageable. Queue is specifically programmed to Ethernet 4 and the DHCP address range of 192.16.1.0/24 which will provide burst as set to only those IP addresses.

- placing a second queue above a Queue to identify a static IP address with separate burst values works. The order of the queues are managed by the router in a top to bottom order.

Bursts
Bursts are used to allow higher data rates for a short period of time. Every 1/16 part of the burst-time, the router calculates the average data rate of each class over the last burst-time seconds. If this average data rate is less than burst-threshold, burst is enabled and the actual data rate reaches burst-limit bps, otherwise the actual data rate falls to max-limit or limit-at.

Let us consider that we have a setup, where max-limit=256000, burst-time=8, burst-threshold=192000 and burst-limit=512000. When a user is starting to download a file via HTTP, we can observe such a situation:




At the beginning the average data rate over the last 8 seconds is 0bps because before applying the queue rule no traffic was passed, using this rule. Since this average data rate is less than burst-threshold (192kbps), burst is allowed. After the first second, the average data rate is (0+0+0+0+0+0+0+512)/8=64kbps, which is under burst-threshold. After the second second, average data rate is (0+0+0+0+0+0+512+512)/8=128kbps. After the third second comes the breakpoint when the average data rate becomes larger than burst-threshold. At this moment burst is disabled and the current data rate falls down to max-limit (256kbps).

see attached Excel burst rate time simulator. Hope it helps