Uppy: Move limiting to different point, to fix StatusBar and other UI issues

Created on 24 Dec 2017  路  10Comments  路  Source: transloadit/uppy

I'm experiencing various issues uploading files in bulk using XHRUpload (through the AWSS3). Just a general question if Uppy is designed to work for uploading big amounts of files?

I'm getting timeout errors (upload stalled for 30 seconds). Does the timeout counter start from the moment it's "prepairing the uploads"? In the case of AWS or Gcloud, this means retreiving the signed urls, which can take some time if we have to do this for many files.

And I'm guessing the dashboard plugin is not the most logical choice in this case.

Bug Improvement

Most helpful comment

Generally speaking, I think it鈥檇 be nice to do a 10K milestone next year, where we try to upload 10k files as well as 10k MBs (so yeah, 10GB ;) through to the whole uppy/server/tusd/transloadit chain and make sure all components can handle it. Not that it鈥檇 be the primary/majority use case that we, but it might help uncover some bugs, memory leaks, optimization kinks that鈥檇 be nice to iron out before 1.0. It鈥檚 something we haven鈥檛 prioritized yet tho so that will explain why you鈥檙e hitting some issues with this number. What鈥檚 your timeframe on this?

All 10 comments

Generally speaking, I think it鈥檇 be nice to do a 10K milestone next year, where we try to upload 10k files as well as 10k MBs (so yeah, 10GB ;) through to the whole uppy/server/tusd/transloadit chain and make sure all components can handle it. Not that it鈥檇 be the primary/majority use case that we, but it might help uncover some bugs, memory leaks, optimization kinks that鈥檇 be nice to iron out before 1.0. It鈥檚 something we haven鈥檛 prioritized yet tho so that will explain why you鈥檙e hitting some issues with this number. What鈥檚 your timeframe on this?

It's the primary use-case of the uploader, (CD's with MRI scans, to be precise), which can have 1000's of files on them.

I've figured out the uploader works a lot better if I put a limit to the concurrent uploads in the XHRUpload component, but this option isn't currently accessible from the AWSs3 plugin if I'm correct. However, if I do this the statusbar isn't displaying the uploads correctly, since it assumes it's only doing "limit"-number op uploads at the time. But I think with a few tweaks it'll be a lot easier on the browser.

However, if I do this the statusbar isn't displaying the uploads correctly, since it assumes it's only doing "limit"-number op uploads at the time.

oh yeah that's a good find! we should apply the limiting at a different point ...

I created a PR for passing XHR options https://github.com/transloadit/uppy/pull/471

@goto-bus-stop That would be great! Let me know if you need any help

@goto-bus-stop I assume once the limiting function is moved to another point, the "upload +### button" issue will be solved, too?

screenshot 2017-12-27 17 18 44

Yeah, it should fix that too!

@goto-bus-stop do you need any help moving the limiting to another point? I don't see it on the changelog list for .23, not sure how much work this is either. Anyway, happy to help - let me know.

tackling this today!

@goto-bus-stop thanks!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

matthewhartstonge picture matthewhartstonge  路  3Comments

NihadOb picture NihadOb  路  3Comments

skunkwerk picture skunkwerk  路  3Comments

evanoberholster picture evanoberholster  路  3Comments

oyeanuj picture oyeanuj  路  3Comments