Skip to main content
Each integration writes what it collects to its own queue on disk, and the gateway uploads from those queues as bandwidth allows. This keeps data safe through network outages, sign-outs, and app restarts.

Upload Limits

Upload bandwidth and parallelism apply to the whole computer. Change them in the desktop app under Settings > Data Ingestion, or remotely from the gateway’s Settings in the web app (see Remote Management). Changes apply immediately. The bandwidth limit applies to file uploads, which include RHEED frames and tool log files. Timeseries uploads go first: while one is in progress, new file uploads wait, so live charts stay responsive. When several integrations have files waiting, the next upload slot goes to the integration with the fewest uploads in progress. Files over 100 MiB upload in 50 MiB parts, so an interrupted transfer resumes from the last completed part.

Disk Buffering

Two advanced settings, present on every integration, bound its queue. Both are in bytes. When the queue nears a limit, the Upload Queue shows a Backpressure badge. When it reaches one, the integration stops accepting new data until uploads drain or disk space frees. Queued data is never discarded to make room.
A full queue means new instrument data is not being collected. For RHEED, frames that arrive while the queue is full are dropped. Size the disk and the limits for the longest outage you need to survive.
Uploads retry automatically after network errors, waiting from 1 second up to 30 seconds between attempts. Data that can’t be uploaded within 30 days is discarded. See Keep the Gateway Running for what happens on sign-out and restart.

When Uploads Fall Behind

On the integration’s page, Health shows Last successful upload, Upload Queue shows what is waiting, and the Advanced view shows Last upload error and Retry attempt.