@SteadyStatus21 Thanks for your reply.
TLS Handshake Timeout error is another topic in this issue. but let's explain why this error has happened.

The Internet, for example, has what is called bandwidth. It is also present in the internet connection (e.g. 4G, LTE) you are using. There is a maximum amount of bandwidth that can be connected at the same time, and you're probably getting more than that at the same time. (The option you are running is -p 1024, so you are using 1024 connections at the same time.)

If this amount is exceeded, the machine will perform scheduling (As a simple explanation, scheduling means waiting for other processes to finish and then restarting them when they are ready) for each connection. The more connections there are, the more scheduling processes occur, and the more machine resources start to be exhausted. This will happen both on your machine and on the server where the image will be distributed.

In other words, the more connections you have when you exceed a certain number of connections, it will be slower your download speed. I plan to remove the -p option in the future and use pget to assign the suitable number.

Currently, I can recommend a number such as -p 6. (I don't know the TCP window size of your machine, so this is just a guess) 1024 is almost the same as attacking the other server.

If you get the same error (TLS Handshake Timeout) with -p 6, please raise the issue again with that purpose.

Thank you.

Uh oh!

Progress Bar freezes #36

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions