Juan Cruz
Juan Cruz
Thanks @michaelsproul for the workaround, I am just wondering how this would work together with lighthouse validator using a remove web3signer, would this key pair conflict in some way?
Great finding guys! any idea when this can make it to unstable branch?
HI @michaelsproul yes we are happy with current memory footprint, great improvement since `v2.5.1` & `v3.0.0` FYI, this chart includes tests with internal versions + latest public releases Thanks! /Juan
Good work guys, this feature got massive improvement in memory footprint compared to `v2.2.1`
@michaelsproul numer of signing request didn't change much, we are running on similar numbers Check before screenshot: and after screenshot: Everything is working with some decrease on `Web3SignerRequestFailed` errors Thanks
@michaelsproul Chart combines signing ops from tekus & lighthouse validators, in this chart, from our test environment, we are having around 4k active keys
I managed to isolate lighthouse signing request and number of requests before & after are not significant: Here we are talking of 2 validators (each one with around 800 active...
Any idea when this PR will be released? Thanks
@michaelsproul yes memory keeps lower since upgrade
Any update here?