This document explains why load time can vary, even when streaming the same application. While it may seem that identical conditions should always result in identical load times, in reality, several environmental and technical factors can cause variations.
Below are the main factors that influence load time and examples to help you understand each scenario.
1. Same App, Same Conditions
When all the following parameters remain unchanged —
-
Same application
-
Same browser
-
Same configuration
-
Same location
-
Same user
-
Same device
— the load time should generally remain consistent.
However, if any of these factors change, the load time can differ. Let’s explore these factors in more detail.
2. Geographic Location
The physical distance between the user and the streaming server impacts latency and loading speed.
Example:
-
If one user streams from Europe and another user streams the same app from Asia, the user in Asia may experience a longer load time because the data must travel farther through the network.
3. Application Size and Complexity
Different applications vary in size, asset count, and overall data load. Larger applications or those containing many high-resolution textures and 3D assets require more time to load.
Example:
-
A simple visualization app may load within 10 seconds, while a detailed architectural demo with complex 3D assets may take 30 seconds or more.
4. Device Performance
The hardware of the user’s device (CPU, GPU, RAM, etc.) affects how quickly the streaming session can start and render frames efficiently.
Example:
-
On a high-performance device, the app may load almost instantly.
-
On a low-end device, it might take 20–40 seconds longer to initialize the same app.
5. Browser Type and Version
Different browsers have varying levels of optimization and WebRTC handling capabilities, which can influence loading behavior.
Example:
-
The app may load faster on Google Chrome compared to Safari because of differences in WebRTC performance and caching.
-
Using an outdated browser version can also add a few seconds to load time.
6. Shared Drive and Concurrent Users
All applications are stored in a shared drive. When a user connects to a streamer, the app is first loaded from that shared drive into the streamer machine.
If multiple users attempt to load applications simultaneously, the shared drive’s bandwidth is distributed among them, resulting in longer load times.
Example:
-
If 5 users are streaming simultaneously, the app may take 15 seconds to load.
-
If 15 users stream at the same time, load time could increase to 25–40 seconds due to shared resource contention.
7. Network Speed and Stability
Unstable or slow internet connections can delay data transfer between the streaming server and the end user.
A temporary drop in bandwidth or high packet loss can cause spikes in load time.
Example:
-
With a 100 Mbps stable connection, load time may be around 10 seconds.
-
If bandwidth drops to 20 Mbps during streaming, it may take 30 seconds or more.
8. Configuration Differences
Each configuration (config) defines parameters such as resolution, input mode, and environment setup. Minor differences in these settings can influence load performance.
Example:
-
A 4K resolution config will naturally take longer to initialize than a 1080p config due to higher data requirements.
Need help?
🛠️ Contact our Support Team
💬 Join the Community on Discord
Follow us on:
Facebook | GitHub | LinkedIn | YouTube
Related content