You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 2, 2018. It is now read-only.
When calling timer.interval(Duration::from_millis(100)), the program takes up almost 100% of the CPU cycles, but after changing the interval from 100 to 101, the CPU usage dramatically drops to nealy 0%. Tested on macOS 10.12 with Rust 1.17.
Here is my code, you can reproduce it with cargo run --release 1000 100 and cargo run --release 1000 101.
The text was updated successfully, but these errors were encountered:
When calling
timer.interval(Duration::from_millis(100))
, the program takes up almost 100% of the CPU cycles, but after changing the interval from 100 to 101, the CPU usage dramatically drops to nealy 0%. Tested on macOS 10.12 with Rust 1.17.Here is my code, you can reproduce it with
cargo run --release 1000 100
andcargo run --release 1000 101
.The text was updated successfully, but these errors were encountered: