Nethermind Pruning

[CMTRACE]

Hey, looking to prune Nethermind or ideally set up online pruning to trigger when disk space is low. (at 250gb for example)

How can this be achieved? under config "Extra Opts" no argument i pass to nethermind through extra opts seems to work every time in the logs its logged as an invalid argument

https://docs.nethermind.io/nethermind/ethereum-client/configuration/pruning

If extra ops isn't working, can we expose the config file to edit through the dappnode UI?

[pablomendezroyo]

Hey! thanks for the suggestion. It looks like the way of triggering the nethermind prunning is through envs vars. We can easily implement the needed envs in the Nethermind package with a nullish value. Finally, you could set the value you want at the package config view and trigger the prune.

This should be implemented in all nethermind networks (goerli, gnosis and mainnet)

@tropicar thoughts?

[CMTRACE]

hey thanks for the reply - are you saying this is configurable now? sorry if i misunderstand

[pablomendezroyo]

No right now but it would be really easy to implement:

1. Add the needed env to the setupwizard. https://github.com/dappnode/DAppNodePackage-nethermind/blob/master/setup-wizard.yml
2. Add the env to the compose file

   DAppNodePackage-nethermind/docker-compose.yml

   Line 14 in fe0f6e2

   environment:

[NelsonMcKey]

Bumping this, because there seems to be quite a bit of demand from the community (and my validator is getting full!)...

@tropicar

[ilcato]

@tropicar, any ETA? I'm reaching ssd limit.

[Archethect]

Same here, would be cool to have it.

[pablomendezroyo]

@dsimog01 lets push this!

[CMTRACE]

Hey is there update on this? I think it would be critical to accompany the update with some help text describing an optimal set up for dappnode to balance disk usage and performance of the nethermind client.

It's very unclear from the nethermind docs what settings would be optimal for a home validator and can cause performance issues and poor user experience if set incorrectly

[ilcato]

@tropicar, @pablomendezroyo any news on this?

[kamilchodola]

Why EXTRA_OPTS not working? It should be as straightforward as setting those flags:
--Pruning.Mode=Hybrid --Pruning.FullPruningThresholdMb=250000 --Pruning.FullPruningTrigger=VolumeFreeSpace
I'm using Extra_Opts for passing data for Seq and Grafana and everything works smoothly so maybe this is just a matter of valid config?

[dsimog01]

@kamilchodola What do you think of adding a boolean env ENABLE_PRUNNING that adds these flags?

[CMTRACE]

@kamilchodola What do you think of adding a boolean env ENABLE_PRUNNING that adds these flags?

I'd argue for freedom to configure different settings.

For example the recent nethermind update has higher performance with more ram assigned as cache but with diminishing returns.

So the cache size needs to be configurable at a minimum. Also the number of cores used for pruning should be configurable as to avoid saturating the cpu and negatively impacting attestations etc.

If there isn't going to be a preset default that is optimal for dappnode hardware, it should be configurable so people can test to see what's right for them (based on the nethermind documentation)

To avoid burdening the package authoring team with constantly ensuring all environment variables are mapped to the options fields in the UI, how hard would it be to have a way for people to edit the compose file of a live package so they are able to add non-default fields themselves?