Welcome to the new Box Support website. Check out all the details here on what’s changed.

Box Status

Chunked Uploads API is slower than normal Uploads API (2 times)

Follow
New post
dangminhthanh36

Hi everyone,

 

I am using .Net SDK to upload file to Box. I compared and see that.

Chunked Uploads API (UploadUsingSessionAsync) is slower than normal Uploads API (UploadAsync) 2 times.

For example: I uploaded file as following

UploadUsingSessionAsync: 9Gb file >> 21m

UploadAsync: 9Gb file >> 7m20s

That case is nomal? UploadUsingSessionAsync API is safe (friendly: retry for the failed part...) but slow,  otherwise UploadAsync is unsafe but faster.

 

Thanks in advance.

0

Comments

1 comment

Date Votes
  • Jason

    Hi ,

     

    Thanks for the message! We would not expect that level of performance hit, but in general the Chunked Uploads API can take longer than a standard Upload API. The reason for this is that the Chunked Uploads API requires so much more from the application - it requires breaking the file up, calculating hashes, and keeping track of chunks to upload them in order.

     

    Additionally, depending on how large the chunks are, you may not reach maximum throughput by the time a chunk completes uploads. For example, if you notice sometimes when you upload larger files, the speed starts out slow but then increases after a few minutes. With chunked uploads, the speed may not "ramp up" all the way before a new chunk is initiated. I know there's a technical term for this, but I don't remember it unfortunately.

     

    The benefit to chunked uploads is absolute reliability. Rather than having to restart a multi-gigabyte upload (for those of us less fortunate and not able upload multiple gigs in <10 mins), a chunked upload will be able to persist/retry individual parts should any individual part fail due to network issues.

     

    Hope that explains it more! 

     

    Thanks,

    Jason

    0
    Comment actions Permalink

Please sign in to leave a comment.