4 ms·

Depending on your read and write patterns, overflowing even every few days might be appropriate, and also obfuscate the creation time [1] more. [1] https://new

• j-pb 2y ago
  Great point, using a u16 is probably the best choice then. As it give locality within 65.53600 seconds (roughly a minute) without exposing sensitive timing information, and should cover most real world write scenarios.
  • j-pb 2y ago
    A small additional improvement might be to also create a random 16bit salt at startup and then xor the timestamp with that, to leak even less information. That way entries will still have locality without leaking ms timestamp info.
    • 1oooqooq 2y ago
      at this point, why not use the creation date (with all that you describe on top) as the primary component of the primary key?
      • j-pb 2y ago
        you only got 128bit, you want most of that to be randomnes, otherwise collisions are much more likely