Benchmarking: forgestress #3812
Merged
Conversation
This file contains 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
deepfire
force-pushed
the
bench-forgestress
branch
4 times, most recently
from
615ad8d to
e8d2ddd
Compare
MarcFontaine
force-pushed
the
bench-forgestress
branch
from
e8d2ddd to
b444577
Compare
deepfire
force-pushed
the
bench-forgestress
branch
3 times, most recently
from
b5129e4 to
1e39765
Compare
deepfire
force-pushed
the
bench-forgestress
branch
from
1e39765 to
8f700c4
Compare
deepfire
force-pushed
the
bench-forgestress
branch
11 times, most recently
from
6478306 to
b404ac8
Compare
deepfire
force-pushed
the
bench-forgestress
branch
from
b404ac8 to
7319ac0
Compare
deepfire
requested review from
denisshevchenko,
jutaro,
MarcFontaine and
cleverca22
as code owners
mgmeier
approved these changes
May 10, 2022
denisshevchenko
approved these changes
May 10, 2022
jutaro
approved these changes
May 10, 2022
deepfire
force-pushed
the
bench-forgestress
branch
from
1d3d3a1 to
eac697d
Compare
|
bors r+ |
iohk-bors bot
added a commit
that referenced
this pull request
May 10, 2022
3812: Benchmarking: forgestress r=deepfire a=deepfire 1. Log analysis has been rewritten as a composition of orthogonal chunks -- micro-ops, with clear inputs and outputs 2. The workbench log output has been clarified 3. Log analysis filters are now specified by profiles 4. Profiles now provide run-time expectations to the workbench -- informed by shutdown slot and tx workload 5. The workbench now enforces the above run-time expectations on the `fixed` scenario profiles (time-bounded) 6. Log analysis can now be requested for runs 7. Runs can be iterated (only makes sense for `fixed` scenario profiles) 8. Genesis handling has been properly moved 9. The profile structure has been cleaned up a lot 10. More intermediate computed values are now specified as part of profile output 11. Log analysis now emits separate components that are easier to use for reports Co-authored-by: Kosyrev Serge <[email protected]> Co-authored-by: MarcFontaine <[email protected]>
|
This has passed CI on the previous run, so merging directly. |
|
Timed out. |
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.
fixedscenario profiles (time-bounded)fixedscenario profiles)