165 releases (19 breaking)

new 0.21.0-alpha.1 Dec 11, 2024
0.20.2 Nov 28, 2024
0.17.0 Jul 8, 2024
0.15.0-alpha.5 Mar 29, 2024
0.4.0 Mar 28, 2023

#495 in Rust patterns

Download history 10832/week @ 2024-08-21 8668/week @ 2024-08-28 8601/week @ 2024-09-04 6848/week @ 2024-09-11 6381/week @ 2024-09-18 5812/week @ 2024-09-25 4327/week @ 2024-10-02 5486/week @ 2024-10-09 6494/week @ 2024-10-16 4381/week @ 2024-10-23 5991/week @ 2024-10-30 5872/week @ 2024-11-06 6795/week @ 2024-11-13 5809/week @ 2024-11-20 6522/week @ 2024-11-27 5840/week @ 2024-12-04

25,821 downloads per month
Used in 71 crates (4 directly)

MIT/Apache

73KB
1K SLoC

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

~0.8–8.5MB
~79K SLoC