Skip to content

Conversation

ANtutov
Copy link

@ANtutov ANtutov commented Aug 14, 2025

Reason:

  • The safe benchmark (txn.get::(...)) measures value length, while the raw benchmark summed key length, producing inconsistent metrics.
  • Without checking the return code, the raw path could silently mis-measure on failures.

Goal:

  • Ensure apples-to-apples comparison between safe and raw implementations.
  • Improve reliability of the benchmark by catching retrieval errors early.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

Successfully merging this pull request may close these issues.

1 participant