Optimize chunk sending/encoding to do work in batches #17

Closed
opened 2024-08-18 12:36:34 +02:00 by liquidev · 0 comments
liquidev commented 2024-08-18 12:36:34 +02:00 (Migrated from github.com)

Right now there's only one encoding thread per chunk, which is a bit lame for performance. Additionally, the WebSocket thread has to send in requests for chunks one by one, which is also lame for performance.

Instead we should request as much work as possible, and then the encoder should distribute that work to multiple threads.

Right now there's only one encoding thread per chunk, which is a bit lame for performance. Additionally, the WebSocket thread has to send in requests for chunks one by one, which is also lame for performance. Instead we should request as much work as possible, and then the encoder should distribute that work to multiple threads.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: liquidex/rkgk#17
No description provided.