LACP can't help for a single flow, Weaver. Depending on the kit and configuration the decision which link in the LAG is used is made via headers at layer 2, 3 or 4.
I pointed to it as a step in the right direction, not an endgame solution.
EDIT: Given the audience, Mr Weaver
I should elaborate.
LACP is Link Aggregation Control Protocol. It does what it says on the tin and works at layer 2. However, the kit implementing it isn't usually aware past at most layer 4, and decides which link to use by hashing the layer 2, 3 or 4 header.
To balance between 2 links on the same flow you have to either be somewhat more clever or be indiscriminate and spray traffic across both links evenly, which requires the kit on the other side to be doing the same - can't make that assumption.
Where carriers require multipath in this manner they use
https://en.wikipedia.org/wiki/Equal-cost_multi-path_routing and layer 3 interfaces, not layer 2.
As you can see from the links there there are some....
complexities that you don't really want to be inflicting on switches.
EDIT 2: My own Virgin Media service uses this. I terminate on a layer 3 device, a CMTS, which in turn has ECMP to its uplinks - here are 4 x 10 G to one of them - it can happily take 8 x 10 G to each of 2 uplinks:
214.50.0.80.in-addr.arpa name = lee2-cmts-13-tenge510.network.virginmedia.net <> 213.50.0.80.in-addr.arpa name = leed-core-2b-xe-802-0.network.virginmedia.net
218.50.0.80.in-addr.arpa name = lee2-cmts-13-tenge511.network.virginmedia.net <> 217.50.0.80.in-addr.arpa name = leed-core-2b-xe-803-0.network.virginmedia.net
222.50.0.80.in-addr.arpa name = lee2-cmts-13-tenge512.network.virginmedia.net <> 221.50.0.80.in-addr.arpa name = leed-core-2b-xe-804-0.network.virginmedia.net
46.241.0.80.in-addr.arpa name = lee2-cmts-13-tenge513.network.virginmedia.net <> 45.241.0.80.in-addr.arpa name = leed-core-2b-xe-805-0.network.virginmedia.net