Benchmark hpgsql against C# and Rust libraries - #55
Merged
Merged
Conversation
So cargo and rustc aren't necessary for the development shell
mzabani
marked this pull request as ready for review
September 6, 2026 12:28
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This increases some of our benchmarks to 17 fields per record, which I guess is a bit too much for most real world queries, but is not bad for a benchmark since it increases the variety of decoded types.
However, I feel like other libraries use
row.get(N)access patterns that penalize them too much compared to hpgsql, so we should probably change benchmarks to use records with fewer fields, and more queries. (OTOH it is a legitimate advantage of hpgsql that it pays only linear-time costs over number of fields per query).