Load time

How long a viewer waits before they can use your Eagle 3D Streaming app, what that time is spent on, and what actually shortens it.

How long does a stream take to load?

SituationTypical wait
Preallocated — already runningUnder 10 seconds
Streamed often, so the app is warm on E3DS machines10–20 seconds
First time it has been streamed20–30 seconds

"Warm" means the machine already holds your downloaded and unpacked build, so the Acquiring and Preparing stages below are skipped. Uploading a new build or version starts every machine cold again.

These are rough, illustrative ranges, not measured guarantees, and the variable is your app. Two applications on identical hardware load at different speeds because of what is in them — how much content, how it is structured, how much has to exist before the first frame. The platform's share of the wait is roughly fixed; yours is not.

What the wait is spent on

  1. Finding a machine

    A machine is assigned to the session, waiting in a queue if none is free. This happens before either of the next two stages.

  2. Acquiring

    Downloading your build to that machine. The viewer sees it as App Acquiring stage: N%.

  3. Preparing

    Unpacking the downloaded build. The viewer sees it as App Preparation stage: N%.

  4. Starting

    Your app launching — the part you control, and usually the largest part for anything substantial.

A preallocated app skips all of that, because the app is already running when the viewer arrives. That is why it is the largest single improvement available and why it costs what it does.

Measuring it

Two ways, and the second is the one worth using.

Shortening it

In rough order of effect:

  1. Load less before the first frame

    Start with a smaller map and bring in the rest afterwards. Unreal's level streaming loads only the parts of the world that are needed, which cuts both the wait and the memory the app holds.

  2. Load in the background

    Asynchronous loading lets the app become usable while the remaining assets arrive, rather than making the viewer wait for all of it.

  3. Preallocate, if the wait genuinely matters

    For a live demo or a public-facing experience, this removes the platform's share of the wait entirely. It costs a machine running continuously, so it is a trade rather than an improvement — both sides of it here.

  4. Show something while they wait

    This does not shorten the wait, and it changes how long it feels. A loading screen with your branding beats a blank frame, which reads as a broken stream.

Last updated