Jul 20, 2026

These tables are logically one in a relational model, but are implemented independently due to very different access patterns. The huge size of each drags down the other in unnecessary paging costs. The new SoA design for GPU optimization was based on this implementation, but because there were so many columns, it had to be generalized. So now the generalization has been backported to the original concept. And for this it gets a decent reduction in lock/read as well, not huge but probably measurable.