Daniel Celeda

> For me its 3 hous vs 7 hours Maybe other way around? :) I hope it doesn't slow down after the change.

> Run after recent change with server with 16 core as that seems to be a bottleneck, duration is snapsync only. > > * Lighthouse: 55 minute. > * Lodestar:...

@asdacap we don't use develop anymore. Could you redirect your PR from develop to master?

@MarekM25 what is the status of this PR?

> > @MarekM25 what is the status of this PR? > > I have to add unit tests, deprioritized because it isn't important after the merge or we can merge...

@marcindsobczak it cannot be "easily changed", that's why we don't have that yet :) It's low priority and at the same time quite risky. We can end up with "synced"...

> Also there is a memory leak somewhere in Pruning if it's triggered manually. > > My Nethermind crashed by OOM with 92GB in VM when I've activated pruning. @kkokosa

Related to https://github.com/NethermindEth/nethermind/issues/4433

> @dceleda @smartprogrammer93 @LukaszRozmej @MarekM25 I don't get it TBH When someone runs Nethermind.Runner without config then is supposed to run Nethermind on mainnet. I don't get a part with...

> I believe the whole idea behind this issue and PR is obselete. It was in the early days of SnapSync when suddenly in the mainnet config snapsync became on...