Details
Description
StripedNodeDocumentLocks currently handles all document IDs the same way.
I assume that we see a lot of updates on 0:/, though. These updates would be blocked if another different ID fell into the same lock stripe (and was being updated).
We currently have 4096, so the likelihood isn't that big; on the other hand, a change doesn't seem to be risky.