The curl problem upload file-CodePudding

In Windows server 2008 R2 environment using curl -t command upload the file to the FTP server, upload speed is only 30-40 MB/S, and through the put command Windows FTP upload files can reach 70-80 MB/S, will system replacement for Windows server 2012 and then use the curl command upload speed can reach 70-80 MB/S, because the curl under the Windows server 2008 R2 system optimization problem, what's the solution?
(QOS is set to 0, close the distance difference compression of what are tried, to use)

CodePudding user response:

refer to the original poster dushao310 response:

in Windows server 2008 R2 environment using curl -t command upload the file to the FTP server, upload speed is only 30-40 MB/S, and through the put command Windows FTP upload files can reach 70-80 MB/S, will system replacement for Windows server 2012 and then use the curl command upload speed can reach 70-80 MB/S, because the curl under the Windows server 2008 R2 system optimization problem, what's the solution?
(QOS is set to 0, close the distance difference compression of what are tried, are not)

FTP. Exe can maximize the use of Windows file cache, eliminate caching interfere with you?

CodePudding user response:

reference 1st floor Pale_Cheung response:

Quote: refer to the original poster dushao310 response:

In Windows server 2008 R2 environment using curl -t command upload the file to the FTP server, upload speed is only 30-40 MB/S, and through the put command Windows FTP upload files can reach 70-80 MB/S, will system replacement for Windows server 2012 and then use the curl command upload speed can reach 70-80 MB/S, because the curl under the Windows server 2008 R2 system optimization problem, what's the solution?
(QOS is set to 0, close the distance difference compression of what are tried, are not)

FTP. Exe can maximize the use of Windows file cache, eliminate caching interfere with you?

Using a cache, you mean this is the bottleneck of hard disk read and write, I feel it should not be the bottleneck of hard drives, with 2012 systems use the curl command can reach 70-80 MB/S, and can ensure the hard disk read and write at a faster rate than the number

CodePudding user response:

refer to the second floor dushao310 response:

Quote: refer to 1st floor Pale_Cheung response:

The
Quote: refer to the original poster dushao310 response:

In Windows server 2008 R2 environment using curl -t command upload the file to the FTP server, upload speed is only 30-40 MB/S, and through the put command Windows FTP upload files can reach 70-80 MB/S, will system replacement for Windows server 2012 and then use the curl command upload speed can reach 70-80 MB/S, because the curl under the Windows server 2008 R2 system optimization problem, what's the solution?
(QOS is set to 0, close the distance difference compression of what are tried, are not)

FTP. Exe can maximize the use of Windows file cache, eliminate caching interfere with you?

Using a cache, you mean this is the bottleneck of hard disk read and write, I feel it should not be the bottleneck of hard drives, with 2012 systems use the curl command can reach 70-80 MB/S, and can ensure the hard disk read and write at a faster rate than the number of

test again, Windows file cache is to directly in the task manager, see the memory,

Discharge the curl using cache, in 2012 to open resmon, look at the entire process, relevant pid resource utilization, CPU, memory, disk, network