Repository navigation
Conversation
I re-ran the suite on the published 5.10.5 asset against podman-compose 1.6.0 and docker-compose 5.5.1, with docker-compose both on the Podman socket and on Docker 29.8.1: 1392 timed runs, none failed. The page now carries both comparisons, the host description the harness records, and why these latencies cannot be subtracted from the 5.7.1 table: the engine on this host got two to three times slower on the multi-container rows, and the 5.7.1 and 5.10.5 binaries run against each other take the same time. It names the one row podup loses (#1947) and the memory growth since 5.7.1 (#1946). chart.py reads the renamed docker-compose-podman column and no longer claims podup leads every scenario. Signed-off-by: Jaro-c <75870284+Jaro-c@users.noreply.github.com> Refs #1946, #1947 Signed-off-by: Jaro-c <75870284+Jaro-c@users.noreply.github.com>
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
1 participant
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.
Brings #1948 to
main, so the benchmark page and the README section people see on the default branch carry the 5.10.5 measurements instead of the 5.7.1 ones. Documentation and the chart script only; the binary is unchanged, so there is no version bump and no tag.Signed-off-by: Jaro-c 75870284+Jaro-c@users.noreply.github.com