You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The second parameter with a value=1 means we run a concurrency level of ... 1, sequential.
I have some wheeling to jump into it but i was wondering if there was a concrete reason to not use more concurrency, or if it is definitely a fixable feature.
The text was updated successfully, but these errors were encountered:
I'm not using concurrency because my server does not support it. If there were a config option for this (so I can set it to 1) it would work for me. I believe that's what other SFTP clients do (ie. Transmit).
Did, it in the last pr, you also have an option to switch to 1 if needed.
But i m somehow disapointed the improvements are not amazing.
At least compared to a manual filezilla/whatever/ transfer with the same concurrency level i find the same overall speed, thus i guess the small improvement result is somehow related to my bandwidth which block to 400.
Let s see.
Hi,
Seems like the task is sending each file one by one.
Making things much slower than -what it could be-.
This seems confirmed by my tries of the task, and also the source code,
https://github.com/thrashr888/grunt-sftp-deploy/blob/master/tasks/sftp-deploy.js
The second parameter with a value=1 means we run a concurrency level of ... 1, sequential.
I have some wheeling to jump into it but i was wondering if there was a concrete reason to not use more concurrency, or if it is definitely a fixable feature.
The text was updated successfully, but these errors were encountered: