Skip to content
This repository was archived by the owner on Apr 21, 2025. It is now read-only.

Conversation

@tropicar
Copy link
Contributor

This PR is to make user-friendly the process of using the prunning mode of nethermind client.

I added the main env var in the setup wizard
@tropicar tropicar linked an issue Dec 13, 2022 that may be closed by this pull request
@CMTRACE
Copy link

CMTRACE commented Dec 16, 2022

I've tested pruning on a seperate machine outside of dappnode with nethermind.

I think there should be some documentation to accompany this.

The nethermind docs are not great for this pruning module, they have acknowledged this on their discord.

Some points from my testing:

  1. The stated 6-24 hours window for pruning on fast and slow hardware respectively is not accurate. On a dappnode using all available processors it still took well over 24 hours to prune.

Re syncing from scratch is faster at the moment. It seems traversing beach node to mirror to a new state db is still quite slow in nethermind. Even in dappnode gen 10 hardware.

2.there is not a good UX in the logging to determine how far along an operator is in the pruning process

  1. There isn't a way to determine how many nodes need mirroring before the process is started so that can't be used as a determination of how long there is to go.

  2. A better explanation than is present on the nethermind docs for the following would save many support requests in dappnode discord:
    A. What is the different between pruning modes, what is generally viewed as optimal for new setups or existing setups
    B. How much space does a dappnode need free to successfully prune
    C. How much and what does more cache ram actually do when it's set in hydrid mode

  3. If the process fails, users need to know to start pruning from the beginning.

@0xt3rtium
Copy link

Realize this is a quite old PR, but was just checking the Nethermind pruning docs and noticed the Hybrid pruning mode. Wouldn't that be the better choice compared to Full pruning mode?

According to Nethermind docs:

Setting Pruning.Mode=Hybrid enables both InMemory and Full modes. InMemory mode helps the node grow at a slower rate compared to Pruning.Mode=Full. With this configuration, Full Pruning is executed less frequently, promoting healthier disk operation. Since Full Pruning is hardware-intensive, this configuration is also beneficial for attestation results.

@heueristik
Copy link

heueristik commented Mar 3, 2024

Please provide this feature. A lot of dappnode users switched to nethermind and everyone will encounter this problem at some point.

@scottrepreneur
Copy link

Anything blocking this?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Nethermind Pruning

6 participants