Force a upb_MiniTable and its fields to be contiguous in memory. #20160
+30
−27
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Force a upb_MiniTable and its fields to be contiguous in memory.
The default size for an empty arena is 256 bytes; if a minidescriptor is 20 bytes long, the arena will allocate another separate block for the minitable fields, which depending on the allocator could increase TLB pressure.
I did try implementing this as a flexible array member on
upb_MiniTable
, but unfortunately that's already used for the fasttable members, and it actually inexplicably showed tiny perf regressions in parsing benchmarks.