Skip to content

feat: access adapter removal , for address_space !=4#2320

Closed
Maillew wants to merge 0 commit intodevelop-v1.6.0from
feat/access-adapter-removal
Closed

feat: access adapter removal , for address_space !=4#2320
Maillew wants to merge 0 commit intodevelop-v1.6.0from
feat/access-adapter-removal

Conversation

@Maillew
Copy link
Copy Markdown
Contributor

@Maillew Maillew commented Dec 12, 2025

  • feature branch for removal of access-adapters, since there are a lot of needed changes, and one PR was getting messy

Closes INT-5621

@codspeed-hq
Copy link
Copy Markdown

codspeed-hq Bot commented Jan 12, 2026

CodSpeed Performance Report

Merging this PR will degrade performance by 83.18%

Comparing feat/access-adapter-removal (6b04b45) with develop-v1.6.0 (6dc3800)1

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

Summary

❌ 8 regressed benchmarks
✅ 16 untouched benchmarks
⏩ 36 skipped benchmarks2

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Mode Benchmark BASE HEAD Efficiency
WallTime benchmark_execute_metered[keccak256] 11.1 ms 47.7 ms -76.72%
WallTime benchmark_execute_metered[revm_snailtracer] 7.3 ms 43.6 ms -83.18%
WallTime benchmark_execute_metered[fibonacci_recursive] 16.9 ms 53.7 ms -68.48%
WallTime benchmark_execute_metered[revm_transfer] 24.9 ms 60.6 ms -58.9%
WallTime benchmark_execute_metered[quicksort] 9 ms 45.7 ms -80.24%
WallTime benchmark_execute_metered[fibonacci_iterative] 14.3 ms 50.3 ms -71.52%
WallTime benchmark_execute_metered[bubblesort] 11.3 ms 47.7 ms -76.41%
WallTime benchmark_execute_metered[sha256] 9.3 ms 45.3 ms -79.46%

Footnotes

  1. No successful run was found on develop-v1.6.0 (95b9cdf) during the generation of this report, so 95fdcd5 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report.

  2. 36 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants