-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dvc push -q is not completely quiet, shows file transfer tqdm progress bars #3314
Comments
@casperdcl could you take a look please? |
That should really not be the case as In terms of this issue, the progress output should be suppressed completely by |
@casperdcl - Appreciate everything you've done with tqdm! Recently, I had something that was running at 200 iterations a second, when I set mininterval to 1 sec, jumped up to 300 iterations a sec. Didn't spend a lot of time determining root cause for the speedup, it could've been caching behavior or something else. I've also seen some minor speedups on other rapidly-iterating scripts when increasing mininterval. Not a huge issue. I'm typically running in Powershell or cmd on Windows 10. |
Hmm interesting as the default No real measurable difference for me (
|
ah also (back to this issue) |
nvm looks like this is a bug |
@WillNichols726 0.85.0 is out with this fix, could you please give it a try and let us know if it fixed it for you? 🙂 |
@WillNichols726 Btw, I suppose you were using |
@efiop - Yeah, was using -q to try and suppress the progress bars that were jumping around. |
Hey guys, love what you've done with DVC.
Had a quick bug that's causing me a little issue. When I use 'dvc push -q' I'm still seeing tqdm progress bars. Wouldn't be a huge issue, but I'm probably pushing 100K 250kb files. This is a local remote, so the transfer speeds are quick. I know in some of my other scripts where I use tqdm, if the iteration time is very small, the tqdm overhead of writing to std::out actually starts to contribute to performance.
dvc version: 0.83.0
os: Windows 10
The text was updated successfully, but these errors were encountered: