Add aarch64-linux system to flake

[locallycompact]

#1404

---

• CHANGELOG updated or not needed
• Documentation updated or not needed
• Haddocks updated or not needed
• No new TODOs introduced or explained herafter

[github-actions]

Test Results

427 tests  ±0   418 ✅ ±0   14m 37s ⏱️ -43s
139 suites ±0     9 💤 ±0 
  5 files   ±0     0 ❌ ±0 

Results for commit 4aec959. ± Comparison against base commit c63cd39.

[github-actions]

Transactions Costs

Sizes and execution budgets for Hydra protocol transactions. Note that unlisted parameters are currently using arbitrary values and results are not fully deterministic and comparable to previous runs.

Metadata
Generated at	2024-04-19 17:16:45.050878449 UTC
Max. memory units	14000000
Max. CPU units	10000000000
Max. tx size (kB)	16384

Script summary

Name	Hash	Size (Bytes)
νInitial	bccf2a430c016bc960fbf31b02694011cd399d20da8882aac9d33611	4110
νCommit	56b0f0b597150e619c76bed60683f3b1e42d7bc0685ed951b882bfc5	1975
νHead	86bff95ba20e9d1d1b34899a56d86bbacc9fed999260b27dcc92d128	9351
μHead	88f533cf67cd0fc93d7d9ccf0a8b1d69ffd1208a825efbebbc1d36ba*	4213

• The minting policy hash is only usable for comparison. As the script is parameterized, the actual script is unique per Head.

Cost of Init Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	4794	8.87	3.39	0.46
2	4995	10.76	4.12	0.49
3	5196	12.55	4.80	0.51
5	5597	16.66	6.39	0.58
10	6605	26.22	10.05	0.73
48	14249	99.77	38.28	1.86

Cost of Commit Transaction

This is using ada-only outputs for better comparability.

UTxO	Tx size	% max Mem	% max CPU	Min fee ₳
1	594	10.24	4.04	0.29
2	777	13.88	5.64	0.34
3	970	17.66	7.29	0.39
5	1339	25.66	10.74	0.49
10	2283	48.19	20.30	0.79
19	3975	97.83	40.79	1.41

Cost of CollectCom Transaction

Parties	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
1	57	544	16.52	6.53	0.35
2	114	654	27.44	10.92	0.48
3	171	764	39.82	15.96	0.62
4	227	878	53.04	21.43	0.77
5	283	984	66.22	26.99	0.92
6	339	1095	83.20	34.05	1.12

Cost of Close Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	536	8.01	3.80	0.27
2	731	9.04	5.67	0.30
3	881	9.66	6.71	0.32
5	1193	11.52	9.19	0.36
10	2144	17.01	16.18	0.50
50	7907	49.50	62.41	1.35

Cost of Contest Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	577	8.20	4.38	0.27
2	820	9.83	6.16	0.31
3	955	10.47	7.20	0.33
5	1157	11.52	8.99	0.36
10	2074	17.37	16.10	0.50
50	8082	52.23	63.76	1.39

Cost of Abort Transaction

Some variation because of random mixture of still initial and already committed outputs.

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	4683	17.09	7.39	0.55
2	4809	27.84	12.14	0.67
3	4847	40.11	17.47	0.81
4	5144	59.47	26.19	1.05
5	5193	76.73	33.71	1.24
6	5296	90.82	39.88	1.40

Cost of FanOut Transaction

Involves spending head output and burning head tokens. Uses ada-only UTxO for better comparability.

Parties	UTxO	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
5	0	0	4627	7.85	3.28	0.44
5	1	57	4661	9.42	4.17	0.46
5	5	285	4797	14.24	7.11	0.53
5	10	569	4966	18.95	10.23	0.60
5	20	1139	5307	31.11	17.62	0.76
5	30	1704	5643	42.43	24.67	0.92
5	40	2276	5985	54.26	31.93	1.08
5	50	2848	6327	65.50	38.95	1.24
5	79	4497	7309	99.62	59.95	1.71

End-To-End Benchmark Results

This page is intended to collect the latest end-to-end benchmarks results produced by Hydra's Continuous Integration system from the latest master code.

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-04-19 17:18:48.133689514 UTC

Baseline Scenario

Number of nodes	3
Number of txs	9000
Avg. Confirmation Time (ms)	21.386191783
P99	115.35227825000003ms
P95	31.12823189999999ms
P50	18.4892835ms
Number of Invalid txs	0

Baseline Scenario

Number of nodes	1
Number of txs	3000
Avg. Confirmation Time (ms)	3.693806916
P99	5.3852279199999975ms
P95	4.4047944ms
P50	3.5970485ms
Number of Invalid txs	0

[wolf31o2]

Nice!

[locallycompact]

@wolf31o2 Any chance you can confirm if it works for you? We are not building aarch64-linux in CI, but we can look into it. If it works for you then it's good to merge.

[v0d1ch]

Do you think we can re-use existing runner to build these artifacts in our CI?

[wolf31o2]

I don't have anything resembling Nix available.

[wolf31o2]

Installing buildx and qemu makes it very possible. We do this for some of our builds. Unfortunately, the Nix magic isn't in my skill set.

[v0d1ch]

@wolf31o2 we should make the binaries available for you to download without you building anything on your side.