Speedtest turns to crap
-
Im running pfsense+ 22.01 on a Dell PowerEdge 140 with Intel Xeon CPU E3-1220 v5 @ 3Ghz (Quad Core) and 8GB of RAM. CPU utilization rarely hits 10%, Memory usage is 15%.
I've tried using the internal Broadcom ports and also Intel quad Gigabit PCIE card.
I've tried two different ISPs (WOW and Verizon 5G).
When I test directly from a laptop:
I can hit 1Gbps (down) on WOW (direct to cable modem with Public IP via CAT6). Upload tops at 50Mbps.
I can hit 980Gbps (down) on VZW (direct to VZW gateway with NAT via CAT6). Upload tops out at 120ish.When I plug either WOW or VZW into my pfsense:
My speedtest turns to crap. Ive tried disabling snort and pfBlockerNG. WOW tops out at 500Gbps down. VZW does slightly better at 550. Why does pfsense+ cut my bandwidth in half?Yes, I've tried tweaking for bufferbloat, doesnt really help. Something on the Pfsense is limiting to half my speed. What else should I check?
-
I assume you mean 500Mbps and 980Mbps there. Though 980Mbps is impossible on a 1G link so it could be the test averaging or you might have a >1G link.
You need to check the per-core loading using
top -aSHat the command line whilst testing.
10% total CPU usage doesn't tell you enough if something you have is single threaded.Steve
-
@stephenw10 said in Speedtest turns to crap:
Though 980Mbps is impossible on a 1G link
I've come close, though this was on a 500/20 connection.
-
@stephenw10 Latest speedtest from fast.com pushes about 300Mbps down and top -aSH shows CPU idle time in low 90s (91-92-93) whilest running the test.
[22.01-RELEASE][admin@pfSense.home.lab]/root: top -aSH last pid: 74947; load averages: 0.31, 0.22, 0.18 up 0+13:56:23 11:55:40 248 threads: 6 running, 225 sleeping, 17 waiting CPU: 0.1% user, 0.1% nice, 0.0% system, 0.1% interrupt, 99.7% idle Mem: 346M Active, 1368M Inact, 625M Wired, 307M Buf, 5505M Free Swap: 16G Total, 16G Free PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND 11 root 155 ki31 0B 64K CPU3 3 819:18 100.00% [idle{idle: cpu3}] 11 root 155 ki31 0B 64K RUN 1 819:04 100.00% [idle{idle: cpu1}] 11 root 155 ki31 0B 64K CPU0 0 819:53 99.67% [idle{idle: cpu0}] 11 root 155 ki31 0B 64K CPU2 2 819:26 99.52% [idle{idle: cpu2}]Also to note, since my initial posting I reconfiged pfSense to not use the integrated Broadcom NICs and instead Im using a 4 port Intel 1G card. Ive tried various combos of moving LAN to Broadcom and WAN to Intel and every combo possible. Currently everything resides on Intel card. I made the following changes to my loader.conf file thinking it would help, but no such luck.
[22.01-RELEASE][admin@pfSense.home.lab]/boot: more loader.conf # agree with Intel license terms legal.intel_iwi.license_ack="1" legal.intel_ipw.license_ack="1" # this is the magic. If you don't set this, queues won't be utilized properly # allow multiple processes to processing incoming traffic hw.igb.rx_process_limit="-1" hw.igb.tx_process_limit="-1" hw.bge.tx_process_limit="-1" hw.bge.tx_process_limit="-1" autoboot_delay="3" net.link.ifqmaxlen="128" -
@stephenw10 No when I connected my laptop directly to the cable modem via RJ45 (without pfsense) I got 1G download speedtest using fast.com on my Cable Internet connection from WOW.
I repeated same test, also without pfsense, via Verizon 5G UW service and got 980Gbps download speed. This proves laptop, ethernet cable, modem on WOW is good. Also VZW gateway is good too.
Problem is definetly something on the pfsense box, just cant pinpoint it
-
None of that stuff has been necessary for some versions now. But likely won't hurt.
If you need custom loader variables though you should put them in /boot/loader.conf.local (create that file). The loader.conf will be overwritten with pfSense changes/upgrades.
You see any errors on the interfaces?
Anything in the system logs?
Clearly not a loading issue.
Steve
