async.Queue rewrite #19

Open
opened 2025-07-30 11:25:31 -07:00 by clo · 0 comments
Owner

across the codebase my actual desire for this queue is to keep the number of work units at a reasonable scale for the CPU. the new queue should support

  • multiple job types (passing a callback per job instead of per queue)
  • specify core count
  • specify job priority
    • allow a "cancel" signal which allows the job to be cancelled and re-queued, for cases where a job takes a lot of CPU resources and it is desired that another job runs
  • headless or TTY interface
    • bonus: implement zig progress API

an implicit dependency of this is making changes to clo/console to make progress reporting a friendlier thing.

across the codebase my actual desire for this queue is to keep the number of work units at a reasonable scale for the CPU. the new queue should support - multiple job types (passing a callback per job instead of per queue) - specify core count - specify job priority - allow a "cancel" signal which allows the job to be cancelled and re-queued, for cases where a job takes a lot of CPU resources and it is desired that another job runs - headless or TTY interface - bonus: implement zig progress API an implicit dependency of this is making changes to clo/console to make progress reporting a friendlier thing.
Sign in to join this conversation.
No labels
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: clo/sitegen#19
No description provided.