Lines Matching refs:Scheduler

28   marl::Scheduler scheduler(marl::Scheduler::Config::allCores());
153 #### Create one instance of `marl::Scheduler`, use it for the lifetime of the process
155 The `marl::Scheduler` constructor can be expensive as it may spawn a number of hardware threads. \
156 Destructing the `marl::Scheduler` requires waiting on all tasks to complete.
158 Multiple `marl::Scheduler`s may fight each other for hardware thread utilization.
160 For these reasons, it is recommended to create a single `marl::Scheduler` for the lifetime of your …
166   marl::Scheduler scheduler(marl::Scheduler::Config::allCores());
178 …marl::Scheduler` may be simultaneously bound to any number of threads, and the scheduler can be re…
185   marl::Scheduler* scheduler = marl::Scheduler::get();
200 … terminating the thread. Forgetting to unbind will result in the `marl::Scheduler` destructor bloc…
204 The `marl::Scheduler` internally holds a number of worker threads which will execute the scheduled …