Unbounded blocksize network test

[evan-forbes]

per recommendation by @cmwaters, it would be valuable to have a test that would continually increase the block size until bandwidth or compute limitations were hit. Provided that we have suitable metric data collection in place, this would give us a better idea of where the bottlenecks are in the entire stack, along with simply providing us with data on how much headroom we have given some set of resources per node in the network.

[amityadav0]

Hi, can i work on this ?

[evan-forbes]

@amityadav0 if this is interesting to you, definitely feel free to work on it alongside our efforts :slightly_smiling_face:

This is part of our larger roadmap for as close to IRL network test (think 1000 nodes), so a canonical version using some yet to be fully fleshed out testing infrastructure, which will require a lot of collaboration and efforts over the course of a few weeks, is something that we will also be working on. tbc though, that does not mean that you can't if this is an interesting topic to you! If doing so, it might be easier to build that test in however you see fit instead of using the canonical infrastructure, and then perhaps we could compare and contribute after the fact.

[amityadav0]

Hi, It looks interesting to me. Understood. Earlier i was thinking it could be done without more nodes. I am new to codebase, will learn more about the code and then give it a try Thanks for the response

[cmwaters]

I think it's pretty important that any performance-based testing simulates as close as possible to what we expect the network to be i.e. if we think the network will have 100 validators, 100 full nodes and 1000 light clients. That's what we should be measuring against.