[PASS] test_print_calldata_agg() (gas: 8237051)
Logs:
Actions: 1, CUs: 1, Calldata (bytes): 3844
Actions: 5, CUs: 5, Calldata (bytes): 16772
Actions: 10, CUs: 10, Calldata (bytes): 32932
Actions: 15, CUs: 15, Calldata (bytes): 49092
Actions: 20, CUs: 20, Calldata (bytes): 65252
Actions: 2, CUs: 4, Calldata (bytes): 13220
[PASS] test_print_calldata_reg() (gas: 11416199)
Logs:
Actions: 1, CUs: 1, Calldata (bytes): 4420
Actions: 5, CUs: 5, Calldata (bytes): 20804
Actions: 10, CUs: 10, Calldata (bytes): 41284
Actions: 15, CUs: 15, Calldata (bytes): 61764
Actions: 20, CUs: 20, Calldata (bytes): 82244
Actions: 2, CUs: 4, Calldata (bytes): 16388
Note: These values are measured for resources with the trivial resource logic and not AnomaPay token transfer resources that have more calldata.
Estimate roughly how this lowers the maximal amount of resources that we can process. Use the calldata measurements in bytes from the benchmarks above.
Context
Calldata gas cost increases are discussed on https://ethresear.ch/t/worst-case-block-size-and-calldata-repricing-for-glamsterdam/23895
ARM transaction objects are calldata heavy:
Note: These values are measured for resources with the trivial resource logic and not AnomaPay token transfer resources that have more calldata.
https://github.com/anoma/pa-evm/actions/runs/21255064652/job/61167150718?pr=458#step:19:32
Resources
Scope
Estimate roughly how this lowers the maximal amount of resources that we can process. Use the calldata measurements in bytes from the benchmarks above.