[ADP-3091] Add memory benchmarks to CI

[paolino]

• Add scripting around the memory benchmark.
• Parameterized node and wallet configuration in cluster with the executable path.
• Add working directory field to wallet launcher.
• Add memory benchmark to the nightly pipeline.

ADP-3091

[Unisay]

This makes a little sense from the outside, is it a temporary state of the things?

[paolino]

No idea, how should it be done ?

[Unisay]

I mean the fact that we have benchmarks in two different namespaces:
packages.benchmarks.cardano-wallet-benchmarks
packages.benchmarks.cardano-wallet

The questions are:

• Why to have wallet benchmarks twice?
• What's the difference between benchmarks.cardano-wallet-benchmars and benchmarks.cardano-wallet ?

[HeinrichApfelmus]

In general, the nix expression packages.benchmarks.cardano-package-name contains the benchmark components of the cabal package cardano-package-name. In this case, we have two cabal packages: cardano-wallet and cardano-wallet-benchmarks.

Why to have wallet benchmarks twice?
What's the difference between benchmarks.cardano-wallet-benchmarks and benchmarks.cardano-wallet?

I have put the benchmarks in cardano-wallet-benchmarks into a separate packages because they do not have a compile-time dependency on cardano-wallet, only a run-time dependency.

I'm not against putting them in the same cardano-wallet.cabal file, but I felt that putting the run-time benchmarks into a separate package would be better for enforcing the phase separation (compile/run).

[Unisay]

Ok, now I see your logic. This is more like a naming issue. I wonder if we can have this distinction "compile/runtime" reflected in the nix derivation names?

[Unisay]

Naming of benchmarks is slightly confusing without an explanation like the one that @HeinrichApfelmus has provided, but its a minor problem.