[#67] Research: reject the absolute-long-offset VarHandle adapter - #121
[#67] Research: reject the absolute-long-offset VarHandle adapter#121peter-lawrey wants to merge 1 commit into
Conversation
Record the scoped conclusion, raw JMH evidence, reproducible prototype patch and independent JDK 21 rerun. The measured absolute-long-offset adapter is rejected without generalising the result to all VarHandle designs.
15971be to
2339c0d
Compare
|
This PR is being closed unmerged because the experiment's result rejects the The durable research archive is available at The evidence supports a narrow conclusion: adapting the current Successor design work is tracked in |
Disposition
Closed unmerged. The experiment was successful, but its result rejects the
implementation proposed by this PR.
Scoped result
The prototype produced the same outputs as the existing Unsafe path in 2,730
exercised comparisons. In the retained JDK 11/17/21/25 matrix, adapting the
current absolute-
long-offsetAccessAPI to byte-array view VarHandles wasslower for XXH3 at every tested size and alignment.
This does not establish that VarHandle is inherently slower. The experiment did
not cover a specialised relative-
int-offset path, XxHash, streaming input,heap/direct
ByteBufferor raw memory. The adapter also initialises and usesUnsafe infrastructure, so it is not an Unsafe-denial fallback.
Durable evidence
The cleaned branch contains a research-only archive rooted at
develop:Archive commit:
https://github.com/OpenHFT/Zero-Allocation-Hashing/tree/2339c0db7fdac48b7564e93aeeb732e6bee0af95/research/issue-67
Follow-up
The complete post-Unsafe architecture is tracked in
#124.
Related to #67. This PR does not merge or close the successor issue.