http://www.dslreports.com/speedtest
Ideally you want to see A to A+'s for bufferbloat.
Test result showing a letter grade worse than a B, probably indicate you have bufferbloat.
That means the device at your bottleneck link (most likely your router) is letting bulk traffic (uploads/downloads) interfere with (and slow down) your time-sensitive traffic (gaming, Skype, Facetime, etc.)
If not then tune.
The DSL Reports Speed Test makes accurate measurements of the download and upload speeds along with the latency during the test.
1. Start a ping to google.com. You’ll see a series of lines, one per ping, typically with times in the 20-100 msec range.
2. Run a speed test simultaneously. To do this, start one of the speed test services below:
3. Watch the ping times while the speed test is running. If the times jump up when uploading or downloading, then your router is probably bloated.
IMPORTANT: The bandwidth settings for the limiters need to be set to the upload/download speed of your internet connection.
It is important to keep in mind that what you are doing in pfSense is setting up a rate limiter.
If you set the numbers lower than your connection will allow, you'll get a great buffer bloat score but you'll slow your network throughput to whatever value you chose.
If you set the number too high, the rate limiter wont come into play and you'll be subjected to the same performance and buffer bloat you had prior to making the changes.
The idea is to let pfSense do the rate limiting closer to home.
Letting your provider do it for you increases latency… and that's what we are really trying to avoid.
So to minimize latency, a recommendation is to first do a speed test to find out what your connection is capable of, then set the bandwidth of the limiters in pfSense to those numbers.
Adjust the queue size adds another dimension to the optimizations.
Someday your connection might receive a speed upgrade and you may forgot to adjust the limiter to make use of it!
Navigate to Firewall → Traffic Shaper → Limiters.
This rule matches ICMP traceroute packets so that they are not matched by the WAN-Out limiter rule that utilizes policy routing.
Policy routing breaks traceroute.
This rule matches ping packets so that they are not matched by the limiter rules.
See bug 9024 for more info.
https://forum.netgate.com/topic/112527/playing-with-fq_codel-in-2-4/896
https://forum.netgate.com/topic/112527/playing-with-fq_codel-in-2-4/815
https://www.dslreports.com/forum/r32261369-Internet-Optimizing-speeds-on-pfSense-with-limiters
https://www.youtube.com/watch?v=o8nL81DzTlU&t=380
http://www.dslreports.com/speedtest
https://community.flexradio.com/flexradio/topics/pfsense-router-tuning-v2-4-4
https://www.bufferbloat.net/projects/bloat/wiki/Tests_for_Bufferbloat/
https://forum.netgate.com/topic/112527/playing-with-fq_codel-in-2-4/815
https://forum.netgate.com/topic/112527/playing-with-fq_codel-in-2-4/856
https://forum.netgate.com/topic/112527/playing-with-fq_codel-in-2-4