-
Notifications
You must be signed in to change notification settings - Fork 424
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
Deeply nested files/directories cause performance issues. #77
Comments
No worries, you aren't being rude, this is a legitimate concern. To be honest I think upload speed is relative. From my university I am able to push about 2GB in about 19 minutes. Your specs seem even more impressive. To start ruling out cases, you can try uploading a big file and see that the upload speed should be good. I suspect it has to do with setting up the respective hierarchies, hence queueing /scheduling might be the bottle neck. Also might you be uploading *.wav files? |
I have pushed another folder containing about 70 files for 750 MB and that took 120 sec. This seems great for few big files, but very slow for numerous small files. The big files were PDFs, the small ones Matlab source files. |
So there you go, it is with the scheduling. I actually cut out a whole lot of parallelism to ensure correctness first. This is was lacking before and causing crashes due to resource exhaustion. Offline, I have been working on getting parallelism in and I have a couple of prototypes. However, I just need to do some heavy testing. |
Got it. Thanks. Looking forward to it.
|
Watch this space: I'll ask for your help in testing it out, if you don't mind. |
Hello folks, |
Please get the latest from master. Thank you very much for reporting this issue and for the discussions everyone, plus the patience. Closing it. Please re-open if it persists. |
I am having this issue with a bunch of source trees. I have been uploading a lot of stuff lately, could google be throttleing me? |
Pushing 605 files for a total of 6 MB took about 16 minutes from a modern SSD over a 100+ mbps university Internet connection. Is this expected?
I was attempting to migrate from Dropbox using this tool. I have hundreds of thousands of small files totaling about 8GB. Is this a feasible use case?
This looks like a great tool and don't want to appear rude. I just want to know if I'm doing it wrong.
The text was updated successfully, but these errors were encountered: