Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

perf: close method-call throughput gap to blead Perl

オープン
  • 何か問題がありますか？
#1,846 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@fglock がすでに取り組んでいます。

2026年10月19日 から。

  • #1850 @fglock による — オープン

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
java, perl
領域
performance

調査の方向性

Start with the measurement contract in issue #1196 and the existing dev/bench/benchmark_method.pl anchor; establish a pinned blead, JDK, source and JAR hashes, and JVM flags before comparing performance. Build diagnostic workloads, then use CPU, allocation, GC, and HotSpot evidence to identify bottlenecks. Done means the anchor reaches at least 1.00x pinned blead with the 95% interval lower bound at or above 1.00x, while meeting issue #1196’s portfolio contract.

索引モデルが issue の本文から書いたものです。

説明

area:performance enhancement

Current state

PR #1843 improves the dev/bench/benchmark_method.pl workload through guarded argument unpacking, cached hash-field cells, reduced runtime and frame lookups, and scalar-result reuse. The remaining parity goal is open.

A fresh sequential run from PR head 0d4f883b8437b843c62b30c49d26ffac2c31a231 produced:

  • perl dev/bench/benchmark_method.pl: 340.14 iterations/s, checksum 399600080000.
  • ./jperl dev/bench/benchmark_method.pl: 267.42 iterations/s, checksum 399600080000.
  • PerlOnJava was 0.786x of system Perl in this single run, so it needs about 27% more throughput to reach parity. Treat these as a current snapshot, not a stable estimate; the host was also running test work.

The comparison used the locally installed Perl, not a pinned optimized blead build. The next phase must establish that reference before making parity claims. Existing profiling has sampled RuntimeCode.apply/applyCachedMethod, generated method bodies, hash-field access, warning-bit lookup, and integer scalar construction. These samples identify candidates; they do not prove which cost limits end-to-end throughput.

Next steps

  1. Build a reproducible method benchmark runner following the measurement contract in issue #1196: pin the Perl blead revision, JDK, JAR/source hashes and JVM flags; use deterministic checksums and operation counts; warm to stability; then collect randomized paired measurement windows and confidence intervals.
  2. Split the anchor into diagnostic workloads for no-op dispatch, one-argument dispatch, blessed-hash reads, integer updates, scalar return, and an equivalent inline body. Keep the original method benchmark as the acceptance anchor.
  3. Profile the stable anchor with CPU, allocation, GC and HotSpot inlining/deoptimization evidence. Report exclusive and inclusive costs and allocated bytes per operation. Continue only with bottlenecks that explain a material share of the anchor or portfolio.
  4. Prioritize general call-boundary or primitive-result improvements from that evidence. Keep guarded fallbacks for @_, caller, context, warnings, ties/overload, eval/debugger, exceptions, lvalue returns, non-local control flow, and escaping values.
  5. Add focused semantic coverage before each runtime change; validate Perl-level tests with system Perl and run JVM/interpreter parity checks. Retain exact-parent failure evidence for each regression.
  6. Measure each candidate against pinned blead and the exact parent. Require the method anchor to reach at least 1.00x blead with a 95% interval whose lower bound is at least 1.00x; also meet the portfolio acceptance contract already recorded in issue #1196 before claiming project-wide performance parity.

Related work

主要言語
Perl
スター
64
フォーク
8
平均マージ
5時間 44分
マージ済み PR（30日）
203

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

fglock/PerlOnJava のほかの issue

fglock/PerlOnJava の issue をすべて見る

似ている issue

Perl の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。