How jofpin/turbit works
Turbit is a small Node.js multicore task-execution library. A caller supplies a function and selects simple execution (replicate the task) or extended execution (process data in chunks); Turbit dispatches work to child processes and returns results with execution statistics. The source excerpt is partial, so the graph omits uncertain internal wiring beyond the documented strategies and visible worker messaging.
Main entry points: turbit.js Turbit API
Components 11
Other components
- Library caller
- User task
- Input data
- Turbit API
turbit.js - Process core
turbit.js - Run strategies
turbit.js - Simple execution
turbit.js - Extended execution
turbit.js - Child processes
- Execution metrics
turbit.js - Results and stats
Connections 17
- Library caller → Turbit API: calls run
- User task → Turbit API: provides function
- Input data → Turbit API: provides items
- Turbit API → Process core: selects process count
- Turbit API → Run strategies: dispatches type
- Run strategies → Simple execution: selects simple
- Run strategies → Extended execution: selects extended
- Process core → Child processes: starts and manages
- Simple execution → Process core: creates tasks
- Extended execution → Process core: creates chunk tasks
- Process core → Child processes: sends tasks
- Child processes → Process core: returns results
- Simple execution → Execution metrics: requests stats
- Extended execution → Execution metrics: requests stats
- Execution metrics → Results and stats: provides statistics
- Run strategies → Results and stats: returns output
- Library caller → Turbit API: calls kill