Skip to content

perf: reuse one file-hash read buffer per thread - #644

Merged
tinder-maxwellelliott merged 1 commit into
Tinder:masterfrom
maxwellE:perf/file-hash-buffer
Nov 9, 2026
Merged

tinder-maxwellelliott merged 1 commit into
Tinder:masterfrom
maxwellE:perf/file-hash-buffer

Conversation

@maxwellE

@maxwellE maxwellE commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

hash_file_into declared a fresh [0; 64 KiB] buffer on every call, so every hashed source file paid for zeroing 64 KiB before the first read, even though most source files are a few hundred bytes. On the large synthetic workspace (16k source files) that memset was a fifth of generate-hashes' instructions.

Keep one zeroed buffer per thread and read into it. The reads, their size and the hashed bytes are unchanged, so hashes are identical.

hash_file_into declared a fresh [0; 64 KiB] buffer on every call, so
every hashed source file paid for zeroing 64 KiB before the first read,
even though most source files are a few hundred bytes. On the large
synthetic workspace (16k source files) that memset was a fifth of
generate-hashes' instructions.

Keep one zeroed buffer per thread and read into it. The reads, their
size and the hashed bytes are unchanged, so hashes are identical.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KJs3XyWhGePPEpsP7LQtfC
@tinder-maxwellelliott
tinder-maxwellelliott marked this pull request as ready for review November 9, 2026 14:38
@tinder-maxwellelliott
tinder-maxwellelliott merged commit 6f449ce into Tinder:master Nov 9, 2026
19 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.

3 participants