perf: split BytecodeInterpreter.execute for default C2 compilation

未关闭
#2,093 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
重构
描述清晰度
描述清楚
活跃度
活跃
技术栈
java

调研方向

Start by reading BytecodeInterpreter.execute(SuspendedInterpreterFrame) and the profiling skill at .agents/skills/profile-perlonjava/SKILL.md; use dev/bench/benchmark_eval_string.pl to reproduce the eval STRING workload. Split the dispatch path while preserving opcode behavior and JVM/interpreter parity, then check HotSpot diagnostics, project tests, and the make gate. Compare randomized paired runs against the exact parent and check representative workloads and startup cost; done means default flags produce effective C2 compilation with a measured improvement and no material regression.

由索引模型根据 Issue 内容生成。

描述

area:backend enhancement

Summary

Split BytecodeInterpreter.execute(SuspendedInterpreterFrame) into smaller dispatch/handler methods so HotSpot's default C2 policy can optimize the eval STRING interpreter path without globally enabling compilation of huge methods.

This is follow-up work to eval performance investigations on master. PR #2059 contains allocation and frame-pooling changes, but its performance effect was small and did not address the dispatch method's JIT compilation limit.

Evidence

On master commit 3e725aa6e1 (Temurin 24.0.2, Apple Silicon), async-profiler sampling of dev/bench/benchmark_eval_string.pl showed BytecodeInterpreter.execute as the largest CPU leaf (199 of 1,694 samples, C1), followed by StatementResolver.parseStatement (59) and CompileAssignment.compileAssignmentOperator (48).

HotSpot compilation diagnostics report the private execute(SuspendedInterpreterFrame) method at 23,790 bytecodes. The default DontCompileHugeMethods policy prevents C2 from optimizing this hot dispatch path; the log also reports it as too large to inline.

As a diagnostic, disabling that policy with -XX:-DontCompileHugeMethods caused the 23,790-byte method to reach C2 level 4. Five randomized default/flag pairs on the same master JAR measured:

Default C2 enabled Speedup
52.4k/s 102.7k/s 1.96x
60.7k/s 98.1k/s 1.62x
65.7k/s 98.3k/s 1.50x
71.2k/s 106.9k/s 1.50x
73.2k/s 114.3k/s 1.56x

Each run executes one million iterations of dev/bench/benchmark_eval_string.pl. The geometric mean paired gain is about 1.60x. Host load caused variance in both modes; all five pairs favored C2.

Goal

Reduce the dispatch method's bytecode size enough that the normal JVM policy compiles its hot path effectively. Prefer extracting cold opcode families and keeping common eval opcodes on a direct, JIT-friendly path. Keep opcode semantics, exception behavior, interpreter state, and JVM/interpreter parity unchanged.

The global -XX:-DontCompileHugeMethods flag is a measured interim option, but this issue is to determine whether a source-level split can get the same or better result without changing HotSpot's huge-method policy for every method in the process.

Acceptance

  • HotSpot diagnostics on supported Java versions show the refactored hot interpreter path gets C2 compilation with default JVM flags.
  • Standard Perl behavior and project-owned tests cover affected opcode families; JVM and interpreter backends remain compatible.
  • Run the repository make gate on the immutable candidate.
  • Compare default-flag performance against the exact parent using randomized paired eval STRING benchmark runs with operation counts/checksums; retain the split only when the paired interval shows a real improvement.
  • Check representative non-eval workloads and startup/compilation cost so a faster eval benchmark does not hide a material regression elsewhere.

Related

主要语言
Perl
星标
67
派生
8
平均合并
5 小时 12 分钟
30 天内合并 PR
131

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

fglock/PerlOnJava 的其他 Issue

查看 fglock/PerlOnJava 的全部 Issue

相似的 Issue

更多 Perl Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。