Skip to content

0.1.8: four uploads at once for each server - #4

Merged
robotastic merged 2 commits into
mainfrom
upload-threads
Nov 6, 2026
Merged

robotastic merged 2 commits into
mainfrom
upload-threads

Conversation

@robotastic

Copy link
Copy Markdown
Contributor

Raises the upload queue's workers from the SDK default of 2 to 4 per server (UPLOAD_THREADS).

Why. Every system that sends to the same server shares one lane of the queue, so with the default all of them share 2 workers. A user on a heavy setup reported about 4800 calls/hr. At that rate each upload has about 1.5 s on average before calls start to wait, which shows up as late delivery on Broadcastify Calls. Broadcastify's upload is two round trips (the details POST, then the audio PUT to S3), so it hits that limit first.

Call timestamps don't change: a backlog only delays delivery.

The change is in this plugin rather than the SDK's QueueOptions::default, so other plugins keep their own defaults.

  • cargo test

🤖 Generated with Claude Code

robotastic and others added 2 commits November 5, 2026 22:15
Every system sending to the same server shares one lane of the queue,
and the SDK's default of 2 workers leaves each upload ~1.5 s at
4800 calls/hr before calls start to wait and reach Broadcastify Calls late.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@robotastic
robotastic merged commit babd4d3 into main Nov 6, 2026
1 check passed
@robotastic
robotastic deleted the upload-threads branch November 6, 2026 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant