Choir

Task Orchestration Framework

Orchestration: the planning or coordination of the elements of a situation to produce a desired effect, especially surreptitiously

Why?

• give: control flow (at macro level)
• get: free scaling (both perf and complexity)

@Ralith:

any time you take control flow away from the user you have a really high usefulness bar to clear

Scalable?

• Way to organize your thoughts, and code
• Separating scheduling from structure

Example

let mut choir = choir::Choir::new();
let _worker1 = choir.add_worker("worker1");
let first = choir.add_task(|| { println!("First"); }).run();
let mut second = choir.add_task(|| { println!("Second"); });
second.depend_on(&first);

What is the problem?

Rust + ECS = …

if you have an advanced ECS, everything looks like a system

ECS-centric approach

Task-centric approach

Choir features

• task dependencies, including from running tasks
• spawning tasks from tasks
• multi- and iter- tasks
• flexible workers

Perf

Executing 100k(!) empty tasks:

• individually: 28ms
• as a multi-task: 6ms

Each task: 60ns to 280ns

Future

• circular dependency detection
  Image Not Showing Possible Reasons

  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported

  Learn More →
• exhaustive testing with Loom
  Image Not Showing Possible Reasons

  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported

  Learn More →
• scheduler for Hecs
  Image Not Showing Possible Reasons

  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported

  Learn More →

Happy tasking!

https://github.com/kvark/choir