discoball
Joined 8 years ago
Karma
21
Submissions
33
Member since
Nov 4
Joined 8 years ago
The title comes across as controversial subjectivism for the sake of attracting attention.
“it is possible for a transaction C to be aborted because it conflicts with another transaction B, but transaction B is also aborted because it conflicts with A (on another resolver), so C "could have" been committed. When Alec Grieser was an intern at FoundationDB he did some simulations showing that in horrible worst cases this inaccuracy could significantly hurt performance. But in practice I don't think there have been a lot of complaints about it.”