-
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
Ci experimentation #923
Ci experimentation #923
Conversation
0e7ba80
to
0671b40
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.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly minor things and I'm happy to try this out!
8213ccb
to
4491e5a
Compare
04c91ed
to
6a758c8
Compare
6a758c8
to
6d325dc
Compare
9ca611a
to
ad5557f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's fair to call this now ci-cabal.yaml
and the other ci-nix.yaml
and have it running along.
Caching seems to look good now as well? Great job!
ad5557f
to
c945243
Compare
Building the static executable is orthogonal to ci the same way building the docker images is so we deal with it the same way by putting it in it's own dedicated workflow.
This is doing the same job as CI but trying to embrace github action pre-installed software on Ubunut images and cache mechanism. At this stage, the idea is to have both CI live together to observe, after some time, what happens because there are quite subtle cache interactions in both strategies. So let's run both, see what happen and if we can learn something from it.
c945243
to
7389789
Compare
This branch introduces an alternative CI process: It's doing the same job as ci.yaml but trying to take benefit of github action
pre-installed software on Ubunut images and cache mechanism.
In my experiments, it's sometimes able to achieve better performance than our current ci, I think it's related to a difference in cache performance between GitHub action and nix.
At this stage, I want us to have both CI live together to observe, after some time, what happens:
Both CI and CI2 rely on subtle caching mechanisms and it's only by running them both that we can appreciate the real difference, if any.
These are the changes introduced:
setup_dev_ubuntu
GitHub action has been introduced to limit copy/pasting ci codeSo let's merge that, run both of them together for two weeks and get metrics out of it.
-> TODO review in two weeks after the merge
Oh, I almost forgot, the first build of this on master will take 1h30 or something and this is expected.