You can do things like have multiple gateway groups and policy route different traffic across different groups but I do not see the algorithm changing.

As far as I know what would have to be done upstream in pf anyway.

You are load balancing disparate connections. pfSense has no way to know how much traffic a connection is going to transfer when the state is created. State creation is when the outgoing interface is selected.

You can mitigate this in your situation somewhat by adding weights to your gateways.

You have one circuit at 220 and one at 37 so a gateway weight of about 6 on the 220 gateway and 1 on the 37 gateway should put 6 out of every 7 states on the 220 circuit.

Again, there is zero way for pfSense to know if that state is going to be part of a speed test or a small web query.

Load balancing shines pretty brightly when you are dealing with lots of users and lots of states. It can give less-than-expected performance with things like a couple speedtest states. That is more to do with misplaced expectations than the underlying algorithm.

Thanks a lot for your reply Derelict, I've added weights as you've suggested and sort of understood how it works. The small explanation on states helped a lot!

I am now always getting 256+ mbps speeds on speedtest, which is what I wanted. A visual representation that I can have the both connections theoretically displayed as one. :)

However, since you mention pfSense not knowing much about what the state will be used for. maybe some kind of better more intelligent algorithm can be added in the future. One that can 'learn', and dynamically allocate those states based on their speeds. Or can this not be done? (I'm no expert at this)

For example, if you run a speedtest once, then over time the algorithm will be able to learn how to best balance out the states based on IP's/ ranges / domain names and the same for other traffic too.

But anyways, thanks again for helping me sort this, I was getting a bit frustrated because sometimes it would show the entire speed available, other times, it would not. This will definitely benefit me in the future.

You can mitigate this in your situation somewhat by adding weights to your gateways.

You have one circuit at 220 and one at 37 so a gateway weight of about 6 on the 220 gateway and 1 on the 37 gateway should put 6 out of every 7 states on the 220 circuit.

Again, there is zero way for pfSense to know if that state is going to be part of a speed test or a small web query.

Load balancing shines pretty brightly when you are dealing with lots of users and lots of states. It can give less-than-expected performance with things like a couple speedtest states. That is more to do with misplaced expectations than the underlying algorithm.

https://www.dslreports.com/speedtest

If you look at the windows showing the speeds in the above test it actually shows you how many streams are used.