Dropbox uploads fast - why is my build upload slower?

Your new build reached Dropbox or Google Drive in five minutes, yet the same zip takes much longer to upload to Eagle 3D Streaming. Usually nothing is wrong with your account or with the upload page: the two are not doing the same amount of work. This page explains the difference, shows how to measure your real connection to the Eagle 3D Streaming storage, and how to skip the upload from your computer altogether.

Dropbox often does not upload the whole file

The Dropbox and Google Drive desktop apps cut every file into small blocks and remember the blocks they already have. When you save a new version of a build, most of it is the same as the last one - so the app sends only the blocks that changed, and the progress bar finishes long before a whole build could have crossed your connection. The file looks fully uploaded, but only a part of it travelled.

An upload to Eagle 3D Streaming sends every byte of the zip, every time. Each build is checked, unpacked and test-launched on its own, so nothing can be skipped. A 5 GB zip is 5 GB of upload.

The path matters too

Your build goes from your browser to the nearest Cloudflare entry point, and from there to the Eagle 3D Streaming storage in Western North America. Dropbox and general speed-test sites use different servers on different routes. Your internet provider can have a good route to one and a congested route to the other, at the same moment.

TestWhat it measuresUseful for a slow upload here?
A general speed test siteThe line to some nearby serverNo - it can show a fast line while the route to the storage is slow
Dropbox / Google Drive upload timeOften only the changed blocks of the fileNo - it can look many times faster than the line really is
Utilities → Connection test in the Control PanelReal 16 MB pieces sent to the Eagle 3D Streaming storage, the same way a build upload sends themYes - the speed and the failures your upload will get

Measure your real upload speed

  1. In the Control Panel, open Utilities and choose Connection test.
  2. Press Start the test. It sends a few 16 MB test pieces - first one at a time, then two, then six - and takes up to about a minute and a half. The test pieces are deleted afterwards and do not use your storage.
  3. Read the table: the speed for each step, how many pieces failed, and how long a 5 GB build would take.
  4. The line under the table names the best setting. Set it in My Account → Settings → Upload settings (pieces at a time) before your next upload.
What the test showsWhat it meansWhat to do
Fast at every step, no failuresThe connection is fineKeep 6 at a time
Failures only at 6 at a timeThe connection cannot hold several uploads togetherChoose 2 or 1 at a time
Slow or failing at every stepThe route to the storage is congested or unstable right nowTry another network or later - or use Upload assistance below

Skip the upload: Upload assistance

If your build is already on Dropbox, Google Drive, OneDrive, Box or your own server, the Eagle 3D Streaming servers can fetch it from there - nothing is uploaded from your computer, and a slow home line does not matter.

  1. Make the file's link open for anyone who has it (Dropbox / Google Drive: "Anyone with the link").
  2. In the Control Panel, open Utilities → Upload assistance.
  3. Type the app name and paste the link to the zip, then press Upload from this link. An app name you already use adds the build as its next version.
  4. The page shows each step: checking the link, downloading, checking the zip, uploading, test launch, and Ready. You can close the page; the build appears in your build list when it is ready. If it stops, the page says at which step and why.

Before downloading, the size is compared with your free storage, so a build that cannot fit stops at once with "needs X GB, Y GB free". Builds up to 50 GB are accepted. Links to private or internal network addresses are refused.

Still slow?

Write to (Email / Discord) with a screenshot of the Connection test table and the time you ran it. The numbers show whether the slowdown is on the route to the storage or somewhere else.

Related

Last updated