Skip to content

Benchmark TryParseRequestHeader instead of the obsolete entry points - #89

Merged
MDA2AV merged 1 commit into
mainfrom
chore/bench-tryparse
Nov 3, 2026
Merged

MDA2AV merged 1 commit into
mainfrom
chore/bench-tryparse

Conversation

@MDA2AV

@MDA2AV MDA2AV commented Nov 3, 2026

Copy link
Copy Markdown
Member

The benchmark harness still called TryExtractFullHeaderROM and TryExtractFullHeaderValidated, which have been obsolete since #81. Building the solution printed CS0618 warnings for both calls.

After this change, the solution builds with no CS0618 warnings. One run on an i9-14900K pinned to one P-core (.NET 10) stays within 4% of the README's tables:

README this run
Contiguous, ~95 B 120 ns 118 ns
Contiguous, 4 KB 750 ns 722 ns
Contiguous, 32 KB 5251 ns 5179 ns
Multi-segment, ~95 B 245 ns 237 ns
Multi-segment, 4 KB 1258 ns 1226 ns
Multi-segment, 32 KB 8695 ns 8338 ns
Chunked, 256 B 19 ns 20 ns
Chunked, 4 KB 115 ns 112 ns
Chunked, 32 KB 826 ns 806 ns

The harness called TryExtractFullHeaderROM and TryExtractFullHeaderValidated, obsolete
since #81, and cleared the request before each call, which the parser does itself since
#76. The multi-segment comment now says that only the header block is linearized (#86).
@MDA2AV
MDA2AV merged commit 3b1148f into main Nov 3, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant