Quote from: Shymaa-Arafat on May 03, 2021, 07:38:37 PM

I know those locality plots here
https://github.com/mit-dci/utreexo/issues/257
r not exactly what u r looking for, but u may find in Utreexo project site the open source and data to do ur own plots/data analysis (they do download the IBD Initial Blockchain Data which is full data of previous 200 Blocks.
.
-Also this site give data about block sizes, no. of txs,... etc
https://blockstream.info/testnet/block/00000000000000167572bba29bdcec2cbb0e6926b61d33233b927d44fb75cc33
.
Hope this helps...

I appreciate the effort, but those are far from what i'm looking for.

Quote from: NotATether on Today at 06:30:57 AM

How would somebody simulate the block size for blocks received by Bitcoin Core to perform these tests though? The blocks are either 1MB or 4 weight units in size so it involves running it in regtest and submitting your own blocks en masse, and then you have to fork Core and change the code to allow for bigger size limits.

Roughly this is what i had in mind,
1. Prepare separate network (with specific block weight)
2. Prepare few fast computer solely to broadcast transaction & mine block
3. Prepare few cheap/low-powered/old computer (e.g. Raspberry Pi and old Intel NUC) used to perform benchmark.
4. On fast computer, perform mining block and broadcast transaction (match block size limit)
5. Measure time to verify block/transaction and CPU, RAM and I/O usage on other computer.

Quote from: NotATether on Today at 06:30:57 AM

And by the way I think that it makes more sense to benchmark resource usage in WUs instead of megabytes since new versions of the client doesn't have a concept of megabyte-denominated block size.

I agree.