Scheduling Slices

1 min read
Suggest an Edit

Overview

Lexum executes transitions in bounded units called slices.


Purpose

Slices ensure:

  • fairness
  • bounded execution
  • scheduler control

Execution Model

A transition runs:

  • until completion
  • or until slice limit reached

Preemption

If limit exceeded:

  • execution yields
  • scheduler resumes later

Example

Lexum
transition heavy_task { step { // long computation } }

This may execute across multiple slices.


Benefits

  • prevents blocking
  • enables fairness
  • supports large computations

Determinism

Slice boundaries are:

  • deterministic
  • consistent across runs