#timer #chrono


Measure how long it takes for a program to execute in different clocks

7 releases

0.1.6 Oct 20, 2020
0.1.5 Jun 20, 2020
0.1.4 Apr 19, 2020
0.1.3 Feb 2, 2020
0.1.2 Dec 6, 2019

#21 in Profiling

39 downloads per month
Used in benchlib-rs


702 lines


Build Status Latest Version Rust Documentation

This crate allows you to measure how long it takes for a program to execute in different clocks. It ports the functions of the boost-chrono and boost-timer libraries.

The following clocks and their corresponding timers are implemented.

  • SystemClock, SystemTimer
  • SteadyClock, SteadyTimer if supported by the system.
  • HighResolutionClock, HighResolutionTimer
  • ProcessRealCPUClock, ProcessRealCPUTimer
  • ProcessUserCPUClock, ProcessUserCPUTimer
  • ProcessSystemCPUClock, ProcessSystemCPUTimer
  • ProcessCPUClock, ProcessCPUTimer
  • ThreadClock, ThreadTimer




Add this to your Cargo.toml:

howlong = "0.1"


let timer = howlong::HighResolutionTimer::new();
// do some computations
println!("{:?} have passed.", timer.elapsed());

let timer = howlong::ProcessCPUTimer::new();
// do other computations
println!("{}", timer.elapsed()); // 5.71s wall, 5.70s user + 0ns system = 5.70s CPU (99.8%)


Licensed under either of Apache License, Version 2.0 or MIT license at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this crate by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.


~23K SLoC