Anton Nashatyrev
Anton Nashatyrev
At the moment I have the prototype (calling it `Heku` aka `Hacker Teku`) which is able to run up to ~1000 distinct virtual nodes on their own distinct IPs (or...
> `N == 2` seems as good as any limit. Right. ... as any limit ` >= 2`
> 2 seems low and might be problematic when trying to sync with in smaller networks. We use a cost based rate-limiter which chooses to rate limit via amount of...
Copying some more thoughts from the discord channel: > 17:11] pineapple: From a performance and throughput optimisation point of view for things such as downloading blocks, I think it's mistake...
Changed the limit from `2` to `32` in this PR
> @Nashatyrev Thanks for leading this work, but does a MAXIMUM_CONCURRENT_REQUESTS param communicate an expectation of rate limiting requirements? I imagined some rough numbers denoted as request count per time...
BTW just thought that with a large `MAXIMUM_CONCURRENT_REQUESTS` (like now `32` or maybe even more larger) we may restrict the number of parallel requests _globally_ across all request types. That...
Teku has also started: https://github.com/PegaSysEng/discovery/pull/72
Looks like a good solution to me! Just a spontaneous idea: may be it could be done in a more generic way? I.e. by attributing _any_ ssz member/structure with a...
Hmm... The sync could be a pretty challenging task then. Custody game and DAS provides just blob _publish_ proof. There is no guarantee on further _possession_ and _retrievability_. To retrieve...