-
Notifications
You must be signed in to change notification settings - Fork 87
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
Build aarch64-darwin binaries #1182
Conversation
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 2023-12-01 16:37:02.91255008 UTC 3-nodes ScenarioA rather typical setup, with 3 nodes forming a Hydra head.
Baseline ScenarioThis scenario represents a minimal case and as such is a good baseline against which to assess the overhead introduced by more complex setups. There is a single hydra-node d with a single client submitting single input and single output transactions with a constant UTxO set of 1.
|
Seems like the produced binaries are not runnable, I have successfully retrieved the produced package but the binaries crash even when given the |
edcbb2d
to
2339640
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.
Not sure about the nix magic but the rest LGTM
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.
Was only double the extension. Fixed now e14bc41 |
e14bc41
to
fa21fa3
Compare
I guess the hydra errors are spurious? We have observed those already in the past IIRC |
Are we ok with darwin builds failing here? Do we want to support it going forward or we are hopping onto silicon train? :) |
Using ldd we can find and copy the runtime dependencies and later use DYLD_FALLBACK_LIBRARY_PATH to point there.
We do not want a directory inside and it was not packaging correctly multiple derivations.
This ensures the resulting derivation has the same stdenv and downstream functions can infer the targetPlatform correctly, e.g. packaging.nix
Tried to use a somewhat consistent and not confusing (not too technical) naming. That is, no system triplets and something users would understand on the top level.
Upload artifact is always zipping the paths provided, so we need to unpack the release archive first.
fa21fa3
to
d43f41c
Compare
🍎 Adds a workflow to build binaries on custom MacOS with Apple Silicon runner (
aarch64-darwin
system)🍎
Packages binary with runtime dependencies into a single archive so users can useDYLD_FALLBACK_LIBRARY_PATH
to run the binaries (without further installing)🍎 Use static linking for third-party libraries on all darwin builds and do some patching (courtesy of @angerman) when packing them up (in a `nix build .#release)
Example builds: