Re: Windows users! Help us test upload performance tuning?
On Sat, 18 Aug 2018, Daniel Stenberg via curl-library wrote: uploading to localhost means this test both encrypts and decrypts on the same CPU. Oops. This might not be accurate actually, since I have 4 (multi-threaded) cores they probably did that on different cores... -- / daniel.haxx.se --- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.html
Re: Windows users! Help us test upload performance tuning?
On Sat, 18 Aug 2018, Daniel Jeliński via curl-library wrote: I don't believe encryption is to blame here, at least not on curl side. I was able to upload 40 MB/s over https on plain 7.60 with 4MB socket buffer. Encryption takes more CPU or hardware to get the job done so if you're CPU bound and/or have huge bandwidth then encrypted transfers will of course be slower. With the same linux machine as I ran the previous tests, but this time against an nginx on localhost: - 7.61.0 $ time curl -sT 4GB -k https://localhost/sample.cgi 5.975s - 7.61.1-DEV (with 64KB upload buffer) 5.128s (780031201 bytes/sec) Uploading over plain HTTP took 1.281 seconds with this buffer size (pretty much exactly 4 times faster). But also, uploading to localhost means this test both encrypts and decrypts on the same CPU. As I showed before, if I upload HTTPS to my web site over a gigabit connection I can saturate it; 100MB/sec. On a six years old desktop PC. -- / daniel.haxx.se--- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.html
Re: Windows users! Help us test upload performance tuning?
W dniu sobota, 18 sierpnia 2018 Jan Ehrhardt via curl-library < curl-library@cool.haxx.se> napisał(a): > We had a real oops when we tested the same 178 MB over plain FTP: > > curl x64 512KB upload buffer FTP: 16 seconds > https upload php uploadprogress : 489 seconds I don't believe encryption is to blame here, at least not on curl side. I was able to upload 40 MB/s over https on plain 7.60 with 4MB socket buffer. --- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.html
Re: Windows users! Help us test upload performance tuning?
Jan Ehrhardt via curl-library (Wed, 15 Aug 2018 22:51:34 +0200): >Network connection: about 200 Mbits/s up, 200ms latency (speedtest.net) >Test file: 178 MB mp4 >Protocol: sftp > >iPad app 32 KB libssh2 buffer: 2147 seconds >iPad app 320 KB libssh2 buffer: 737 seconds >Filezilla (out-of-the-box): 967 seconds >curl x64 512 KB upload buffer: 1154 seconds We had a real oops when we tested the same 178 MB over plain FTP: curl x64 512KB upload buffer FTP: 16 seconds https upload php uploadprogress : 489 seconds % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 176M0 0 100 176M 0 11.0M 0:00:16 0:00:16 --:--:-- 13.6M start:2.062000 total:16.01500a0 Unencrypted uploads are legally (the HIPAA act) prohibited, but the price for encryption is really high. -- Jan --- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.html
Re: Windows users! Help us test upload performance tuning?
On Tue, 14 Aug 2018, Daniel Stenberg via curl-library wrote: Update! I would like us to... 1. Change to alloc-on-demand for this buffer. It is used for a few non-upload things, but it only needs to be this big for actual uploads, and most transfers are not. That'll save (almost) 16KB for all download-only handles. 2. Enlarge the default upload buffer size to 64KB. These two steps have now been done and pushed to master. 3. Add a CURLOPT_UPLOADBUFFERSIZE option that allows users to set their preferred size, from 16KB up to perhaps a few megabytes. I intend to write upp a pull-request for this and queue for merging in the next feature window after the pending release on September 5. -- / daniel.haxx.se --- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.html
