Skip to content

53-bit SessionID collision risk, is it a problem? #680

Answered by streamich
tsukkiren asked this question in Q&A
Discussion options

You must be logged in to vote

Hi @tsukkiren, the 53-bit session IDs (sid) should not be a problem. I think even smaller values would work.

The reason for choosing 53-bit values is because it is the largest numeric value in JavaScript with which one can performantly work with. Storing and working with 128-bit UUID is inefficient. There are storage costs, but also runtime costs: all algorithms need to constantly do sid comparisons and having a sid in a number is the most efficient way.

Also, runtime memory costs, all document nodes and RGA chunks have an ID assigned to them, when a document with thousands of nodes is loaded, it is thousands of nodes times the number of bytes the sid consumes. If the sid is represented b…

Replies: 1 comment 9 replies

Comment options

You must be logged in to vote
9 replies
@tsukkiren
Comment options

@tsukkiren
Comment options

@streamich
Comment options

@tsukkiren
Comment options

@streamich
Comment options

Answer selected by streamich
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #675 on July 28, 2024 07:56.