Improve key decryption times for validator client keystores #6946
Labels
meta-investigate
Issues found that require further investigation and may not have a specific resolution/fix
scope-performance
Performance issue and ideas to improve performance.
scope-ux
Issues for CLI UX or general consumer UX.
Problem description
Reference: https://discord.com/channels/593655374469660673/1197575814494035968/1261285696157782116
As of July 12, 2024, the EF DevOps team using kurtosis for their tests require loading 64 validator keys to the client for each test seeking a faster solution. Although improvements such as #4179 was implemented to improve this UX, data shows as of today we are still lagging behind comparatively to other client implementations.
Currently, we use an already optimized cryptography library (https://github.com/ethereum/js-ethereum-cryptography), but we should investigate how to further get to a baseline closer to Teku at ~3s to a standard acceptable by larger node operators which run hundreds/thousands of keys per client instance.
Solution description
Investigate a solution.
Additional context
Run kurtosis locally with other clients to observe key decryption times:
kurtosis run github.com/ethpandaops/ethereum-package --args-file https://raw.githubusercontent.com/ethpandaops/ethereum-package/main/.github/tests/geth-all.yaml
The text was updated successfully, but these errors were encountered: