test_worst_msize()¶
Documentation for tests/benchmark/test_worst_compute.py::test_worst_msize@v5.1.0.
Generate fixtures for these test cases for Osaka with:
fill -v tests/benchmark/test_worst_compute.py::test_worst_msize -m benchmark
Test running a block with as many MSIZE opcodes as possible.
The mem_size parameter indicates by how much the memory is expanded.
Source code in tests/benchmark/test_worst_compute.py
297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 | |
Parametrized Test Cases¶
The interactive table below is also available as a standalone page.
| Test ID (Abbreviated) | mem_size |
|---|---|
| ...fork_Prague-state_test-mem_size_0 | 0 |
| ...fork_Prague-state_test-mem_size_1 | 1 |
| ...fork_Prague-state_test-mem_size_1000 | 1000 |
| ...fork_Prague-state_test-mem_size_100000 | 100000 |
| ...fork_Prague-state_test-mem_size_1000000 | 1000000 |
| ...fork_Prague-blockchain_test_from_state_test-mem_size_0 | 0 |
| ...fork_Prague-blockchain_test_from_state_test-mem_size_1 | 1 |
| ...fork_Prague-blockchain_test_from_state_test-mem_size_1000 | 1000 |
| ...fork_Prague-blockchain_test_from_state_test-mem_size_100000 | 100000 |
| ...fork_Prague-blockchain_test_from_state_test-mem_size_1000000 | 1000000 |
| ...fork_Osaka-state_test-mem_size_0 | 0 |
| ...fork_Osaka-state_test-mem_size_1 | 1 |
| ...fork_Osaka-state_test-mem_size_1000 | 1000 |
| ...fork_Osaka-state_test-mem_size_100000 | 100000 |
| ...fork_Osaka-state_test-mem_size_1000000 | 1000000 |
| ...fork_Osaka-blockchain_test_from_state_test-mem_size_0 | 0 |
| ...fork_Osaka-blockchain_test_from_state_test-mem_size_1 | 1 |
| ...fork_Osaka-blockchain_test_from_state_test-mem_size_1000 | 1000 |
| ...fork_Osaka-blockchain_test_from_state_test-mem_size_100000 | 100000 |
| ...fork_Osaka-blockchain_test_from_state_test-mem_size_1000000 | 1000000 |