-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Open
Labels
A-tokioArea: The main tokio crateArea: The main tokio crateM-timeModule: tokio/timeModule: tokio/time
Description
We recently added an alternative timer implementation in Tokio for better multicore scalability, and we’d love to know what you think! If you’ve tried out the new timer, please share your story.
tokio::runtime::Builder::enable_alt_timer
let runtime = Builder::new_multi_thread()
.enable_alt_timer() // <-- enable the alternative timer
.build()
.unwrap();What can you talk about? Pretty much anything, including:
- Where and how you tried the alternative timer
- What feels different compared to the traditional timer
- Any speed ups, slow downs, or bugs you’ve spotted
- Cool benchmarks, numbers, or logs (or just vibes!)
- Anything that surprised you, confused you, or didn’t work as expected
- Stuff you wish the timer did better or ideas you have
Seriously, any details or thoughts are super helpful. Let us know so we can make Tokio even better for you and everyone else. Thanks for helping out!
Reference:
- Root Issue: Reduce contention in timer driver
- RFC: RFC: Delayed cancellation of timer
- Design Document: Desgin document of the alternative timer
- Pull Request: time: add alternative timer for better multicore scalability
mox692, withzombies, dacozai, jiangzhe and jlizen
Metadata
Metadata
Assignees
Labels
A-tokioArea: The main tokio crateArea: The main tokio crateM-timeModule: tokio/timeModule: tokio/time