Post tx-cost benchmark results verbatim into PR

[ch1bo]

❄️ Adds a github action to publish the benchmark results

❄️ Reduce number of data points in tx-cost

[github-actions]

Unit Test Results

    5 files  ±0    80 suites  ±0   6m 29s ⏱️ +16s
213 tests ±0  211 ✔️ ±0  2 💤 ±0  0 ❌ ±0 

Results for commit 4eeaa0c. ± Comparison against base commit e69644a.

♻️ This comment has been updated with latest results.

[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	2022-05-05 08:11:52.005469248 UTC
Max. memory units	14000000.00
Max. CPU units	10000000000.00
Max. tx size (kB)	16384

Cost of Init Transaction

Parties	Tx size
1	4646
2	4845
3	5044
5	5445
10	6446
30	10447
59	16248

Cost of Commit Transaction

Uses ada-only UTxO for better comparability.

UTxO	Tx size	% max Mem	% max CPU
1	5862	17.98	8.81

Cost of CollectCom Transaction

Parties	Tx size	% max Mem	% max CPU
1	12000	20.77	11.21
2	12682	40.90	22.52
3	12561	53.92	29.59
4	13332	84.39	46.92

Cost of Close Transaction

Parties	Tx size	% max Mem	% max CPU
1	7681	7.34	3.95
2	7948	9.83	5.27
3	7906	8.59	4.59
5	8331	14.78	7.88
10	9450	23.35	12.46
30	12458	48.67	25.91
94	16111	0.00	0.00

Cost of Abort Transaction

Parties	Tx size	% max Mem	% max CPU

Cost of FanOut Transaction

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

UTxO	Tx size	% max Mem	% max CPU
1	11530	8.41	4.87
2	11624	12.34	7.17
3	11630	13.63	7.91
5	11696	16.16	9.33
10	11863	23.98	13.85
50	13240	83.92	48.28
100	14863	52.94	32.37
100	14888	53.19	32.51

[ch1bo]

@abailly-iohk what do you think about this? Shall we move to just ada-only utxos and simplify the results by having a single dimension?

[abailly-iohk]

Yeah, makes a lot of sense, let's do that

[abailly]

LGTM. This begs for outputting the benchmark's results in JSON for easier manipulation and formatting, so that we can only publish the highest values for each type of tx but that's totally addressable in another PR

[abailly]

typo: remove is

[abailly]

nice variable name :)

[KtorZ]

Maybe the Merkle-tree results are a bit off-topic? We could move them back to the plutus-merkle-tree package and leave them there.

[ch1bo]

Maybe the Merkle-tree results are a bit off-topic? We could move them back to the plutus-merkle-tree package and leave them there.

I would agree, but was not prioritizing this work for now. There is an item for this in our red bin

Edit: I see you have addressed this. Nice