-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor Outcome algebra #1340
Refactor Outcome algebra #1340
Conversation
488fbad
to
116c866
Compare
Transactions CostsSizes and execution budgets for Hydra protocol transactions. Note that unlisted parameters are currently using
Script summary
Cost of Init Transaction
Cost of Commit TransactionThis is using ada-only outputs for better comparability.
Cost of CollectCom Transaction
Cost of Close Transaction
Cost of Contest Transaction
Cost of Abort TransactionSome variation because of random mixture of still initial and already committed outputs.
Cost of FanOut TransactionInvolves spending head output and burning head tokens. Uses ada-only UTxO for better comparability.
End-To-End Benchmark ResultsThis page is intended to collect the latest end-to-end benchmarks results produced by Hydra's Continuous Integration system from the latest Please take those results with a grain of salt as they are currently produced from very limited cloud VMs and not controlled hardware. Instead of focusing on the absolute results, the emphasis should be on relative results, eg. how the timings for a scenario evolve as the code changes. Generated at 2024-03-08 07:10:41.040534756 UTC Baseline Scenario
Baseline Scenario
|
Test Results416 tests - 2 408 ✅ - 2 13m 51s ⏱️ +3s Results for commit a2b7673. ± Comparison against base commit 7bfd3c5. This pull request removes 2 tests.
♻️ This comment has been updated with latest results. |
This ensures that `Error` outcomes do not allow state changes, while `Wait` may not have any side effects. Smart constructors and the Semigroup instance still result in some form of DSL in the HeadLogic.
These are not really needed as we do test the JSON definition against the logs.yaml schema and the sample size was very small anyways.
This ensures that
Error
outcomes do not allow state changes, whileWait
outcomes terminate the "line of effects".Smart constructors and the Semigroup instance still result in some form of DSL in the HeadLogic.