High memory usage when running query stake-snapshot and others.

[CarlosLopezDeLara]

Investigate. There might be some way to reduce this by returning results more eagerly. High memory usage when running

• query stake-snapshot --> Optimise query stake snapshot command #4179
• query leadership-schedule --> Merge New query GetPoolDistr ouroboros-network#3932 before --> Optimise query leadership schedule command #4250
  Waiting for (link to PR) to be merged first
• query pool-params --> New query pool-state command #4170
• query ledger-state --> More memory efficient query ledger-state command #4205

---

Reference issues:

#2717
#4128

---

Additional information

---

Acceptance Criteria

AC stake snapshot

• Return the total active stake on the system and the pool stake for the last three stake snapshots
• Do not download the entire ledger state to obtain the stake snapshots
• Command takes less than 5s to return results on a machine that meets the required specs
• Uses less than 12G of RAM

AC leadership schedule

• Leadership schedule returns valid JSON to stdout and cbor to file
• Running leadership-schedule takes less than 30 seconds
• Uses less than 12G of RAM

AC pool-state

• This command obsoletes pool-params query
• Pool-params executes pool-state with a notification to the user about the new command
• Pool-state returns a JSON of futurePoolParams, poolParams, and retiring
• Runs in less than 5 seconds
• Uses less than 12 GB

AC Ledger state

• Keeps returning JSON to stdout
• Uses less than 16 GB

[dorin100]

When we say in the Acceptance Criteria "uses less than X GB", I suppose this refers to the recommended specs, right? We are interested to make clear to the users what are the min specs they need in order to have these functionalities working.

"pool-state" is a new cli command?

[CarlosLopezDeLara]

Resolved by

#4179
IntersectMBO/ouroboros-network#3932
#4250
#4170
#4205