You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Holesky, the watcher takes about 8GiB of ram to be able to watch the entire network, as the entire data set is a few hundreds MiB, there may be way to reduce the footprint by trying to explicitly delete a bunch of dicts/sets after use.
The text was updated successfully, but these errors were encountered:
I guess this could help.
With the GET endpoint, it was more convenient to retrieve all validators instead of a (potentially very big) subset.
==> Big memory footprint, especially on Holesky.
With the POST endpoint, it will be simpler to retrieve a subset of validators.
On Holesky, the watcher takes about 8GiB of ram to be able to watch the entire network, as the entire data set is a few hundreds MiB, there may be way to reduce the footprint by trying to explicitly delete a bunch of dicts/sets after use.
The text was updated successfully, but these errors were encountered: