Skip to content
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

Closed
jpambrun opened this issue Mar 3, 2015 · 9 comments
Closed

Deeply nested files/directories cause performance issues. #77

jpambrun opened this issue Mar 3, 2015 · 9 comments

Comments

@jpambrun
Copy link

jpambrun commented Mar 3, 2015

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.

@odeke-em
Copy link
Owner

odeke-em commented Mar 3, 2015

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?
Thank you for reporting this. Resolving this surely will improve user experience.

@jpambrun
Copy link
Author

jpambrun commented Mar 3, 2015

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.

@odeke-em
Copy link
Owner

odeke-em commented Mar 3, 2015

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.

@jpambrun
Copy link
Author

jpambrun commented Mar 3, 2015

Got it. Thanks. Looking forward to it.
On Mar 3, 2015 4:06 PM, "Emmanuel Odeke" notifications@github.com wrote:

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.


Reply to this email directly or view it on GitHub
#77 (comment).

@odeke-em
Copy link
Owner

odeke-em commented Mar 3, 2015

Watch this space: I'll ask for your help in testing it out, if you don't mind.

@odeke-em odeke-em changed the title Performance issues Deeply nested files/directories cause performance issues. Mar 3, 2015
@odeke-em
Copy link
Owner

Hello folks,
Thank you very much for your patience. I got time this weekend to take a look at how to resolve this and I have spun up a work in progress PR #210 to address it. Please take a look at it if interested.

@odeke-em
Copy link
Owner

odeke-em commented Aug 4, 2015

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.

@odeke-em odeke-em closed this as completed Aug 4, 2015
@gauteh
Copy link

gauteh commented Dec 15, 2015

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?

@odeke-em
Copy link
Owner

Hey @gauteh please take a look at #480

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants