107 releases (14 breaking)

new 0.16.0 May 16, 2024
0.15.1 Apr 11, 2024
0.15.0-alpha.5 Mar 29, 2024
0.12.0-alpha.2 Dec 26, 2023
0.4.0 Mar 28, 2023

#617 in Rust patterns

Download history 1047/week @ 2024-01-25 1052/week @ 2024-02-01 1220/week @ 2024-02-08 3711/week @ 2024-02-15 4193/week @ 2024-02-22 5629/week @ 2024-02-29 4930/week @ 2024-03-07 4835/week @ 2024-03-14 2980/week @ 2024-03-21 2998/week @ 2024-03-28 4272/week @ 2024-04-04 6274/week @ 2024-04-11 5399/week @ 2024-04-18 4842/week @ 2024-04-25 5221/week @ 2024-05-02 3993/week @ 2024-05-09

20,620 downloads per month
Used in 45 crates (4 directly)

MIT/Apache

15KB
145 lines

TUID: time-based unique identifier

Part of the rerun family of crates.

Latest version Documentation MIT Apache

TUID:s are 128-bit identifiers, that have a global time-based order, with tie-breaking between threads. This means you can use a TUID as a tie-breaker in time series databases.

Implementation

TUID is based on two fields, both of which are monotonically increasing:

  • time_ns: u64
  • inc: u64

time_ns is an approximate nanoseconds since unix epoch. It is monotonically increasing, though two TUID:s generated closely together may get the same time_ns.

inc is a monotonically increasing integer, initialized to some random number on each thread.

So the algorithm is this:

  • For each thread, generate a 64-bit random number as inc
  • When generating a new TUID:
    • increment the thread-local inc
    • get current time as time_ns
    • return TUID { time_ns, inc }

Performance

On a single core of a 2022 M1 MacBook we can generate 40 million TUID/s, which is 25 ns per TUID.

Future work

For time-based exploits (like Meltdown/Spectre) time_ns should probably be rounded to nearest millisecond for sensitive systems. The last ~20 bits of time_ns can be filled with more randomness to lessen the chance of collisions.

Dependencies

~290–780KB
~14K SLoC