Ghostdragon wrote:
If you have more than one internet connection then it will benefit from more connections most only have one so connecting multiple times is of no benefit
sorry but this is just wrong...
for example a website, every item on the website, every jpg, every icon, every script, everything gets loaded individually with its own connection!
and thats totally normal behavior.
and on my end the 5 parallel connections speed things up for me.
it just means it loads 5 files at the same time and not just one....
on the a3s client the shown download speed goes kinda crazy when you use more than 1 connection because it calculates its average speed by its actual workload.
and if there are a lot of 1kb files (keyfiles) it cant reacht speeds up to 2MB/s , because the file already transferred after 1kb/s.
so thatswhy it jumps up and down...
so i'am interested if it actually took longer or you assumed it because it showed you higher estimated time?!
Massey wrote:
not sure if that is how it works:
The server limits the number of connections that can be made per client.
Each connection can download a file simultaneously. So I would suspect
the repo is limiting to <5; still not sure why that would make
choosing 1 quicker than choosing 5 on the client.
the client is limiting, its a value you can predefine on the server side of the repo, but the limit is actually done by your a3s client.
the server can easily handle around 20 people downloading with 5 connections at the same time (the bandwidth wont be good, but the server will be still bored)
there might be cases where 1 connection will be faster but thats normally a client side thing