Repository navigation
docs: update Aerospike comparison for v0.3.0 io_uring - #473
Merged
Merged
Conversation
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 13 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
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
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.
Update the stable Aerospike report with the completed Lavik v0.3.0 io_uring comparison: A/B/C/D at 100K and unlimited, covering 16 formal 300-second windows. Refresh both languages, throughput and p99.9 figures, reproduction commands, and the main README description.
The report documents the measured storage layouts and CPU allocation: Lavik uses six full raw NVMe devices while Aerospike uses a RAID0 partition; the 32-vCPU client assigns CPUs 0–15 to YCSB. It retains the A READ tail-latency tradeoff alongside the throughput gains.
Raw logs, metadata, checksums, validation and chart generation are archived separately in lavik-agent. This PR contains only Markdown and SVG files; reproduction instructions are inline in each report.
Validation: reconciled 16 formal windows and 28 operation rows with raw logs, checked recovery receipts and all archived file hashes, checked Bash syntax and local links, parsed and visually inspected both SVGs, and passed git diff --check. Uses existing completed measurements; no benchmark rerun.