Repository navigation
Add the m1 command and the first M1 numbers of rupg - #22
Merged
Merged
Conversation
This was referenced Oct 7, 2026
Closed
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.
Part of #2.
What changes
rupg-bench m1, the in-process driver of spec/22 §22.12. It links therupgfacade at the commit ofpins.toml(238dd51, the head of tamnd/rupg after #130) and has four steps:empty,latency,throughputandrecovery. A test checks that the commit inCargo.tomland the commit inpins.tomlare the same.recoverystartsrupg-bench m1-fillin a child process. The child updates 256 rows of 2,000 bytes in each commit until 1 GiB of values is in the log, and it exits with no close. The driver then drops the file from the page cache withdd iflag=nocacheand times the open that replays the log. The report haslog_bytesfromrupg check.reports/<date>/<commit>-<machine>-m1.mdwith a JSON file. The commit in the name is the rupg commit.m1.reports/2026-10-07/. They are smoke runs and not baselines.Test
srvtestpassed on server1 at the head of this branch: fmt, clippy, cargo deny and 71 tests. Both runs were on 2026-10-07 at about 19:35 UTC, at rupg 238dd51.At rupg aed939c, before #129 and #130, the open on server1 took 15.33 s.
Notes
fdatasynctime of the disk and say nothing about a reference machine. The driver does not print thefdatasyncp50 of the device yet, so the latency line of M1: Storage and commit floors #2 stays open.gpcis not available, so the throughput line of M1: Storage and commit floors #2 stays open, and so does the PostgreSQL 18.6 commit curve next to it.