Best chunk-size dynamics/management method?

[IEWbgfnYDwHRoRRSKtkdyMDUzgdwuBYgDKtDJWd]

Checklist

• I'm asking a question
• I've looked through the README and FAQ for similar questions
• I've searched the bugtracker for similar questions including closed ones

Question

As of right now, I have a bash script with http-chunk-size as a variable, so I can just do

script.sh download.url 300k

and if that is too slow, or if i can go faster with a larger chunk size, i will just terminate the script and retry it changing the chunksize variable. after a few tries, i settle on a sweet spot.

there is no science to this, and the best chunk size is always dependent on multiple factors like which server i am downloading from, time of day, etc etc.

i was thinking of going full blown rube goldberg machine with a script that downloads with a chunk size for a few seconds and quits, logs the time/speed of the small bit downloaded, pipes that into a variable, then does it again with a different size.. and after i have two different test runs with different chunk sizes, pipe that into an equation to find the average and come up with a best guess for the best chunk size off of that..

but wanted to check here before i do all that crap. thanks.

[IEWbgfnYDwHRoRRSKtkdyMDUzgdwuBYgDKtDJWd]

really not seeing the duplicate.