Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

perf: quantify memory costs and broaden call-path evidence after #1870

Aberta
  • Algo errado?
#1,885 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
35/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
java, perl
Domínio
performance

Direção de pesquisa

Read the follow-up requirements in issue #1885 and the report at dev/bench/reports/issue-1863-pr-port-full-14pair-bleed.json first. Compare memory metrics against exact origin/master, profile direct, coderef, and method calls, then stress argument-array pooling for bounds and escaped-value retention. Done means reproducible comparison reports and environment manifests cover these checks.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

The measured throughput acceptance criteria from #1863 are now met by the candidate in PR #1870. The exact pinned-blead 14-pair portfolio reports PerlOnJava/Perl geometric means of 1.059x for the method anchor (95% interval 1.040–1.088), 1.547x for closure (1.524–1.564), and 1.100x for bit-packed Life (1.058–1.167). The report is dev/bench/reports/issue-1863-pr-port-full-14pair-blead.json.

The broader memory and call-path investigation in #1863 is not complete. Track those remaining items here:

  • Compare allocation per operation, post-GC live heap, GC cost, and peak RSS against exact origin/master under the same fixed heap and workload.
  • Profile ordinary direct calls, coderef calls, and method calls outside the stable-hash acceptance shape; identify inclusive/exclusive dispatch, frame, argument, and result costs.
  • Verify retained argument-array pooling stays bounded and does not retain escaped values under repeated stress.
  • Preserve reproducible reports and environment manifests for each comparison.

This follow-up does not change the measured 1:1 result for the three defined throughput workloads. It tracks the remaining memory and generality work separately.

Linguagem predominante
Perl
Estrelas
65
Forks
8
Merge médio
6h 1min
PRs com merge (30d)
189

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de fglock/PerlOnJava

Todas as issues de fglock/PerlOnJava

Issues semelhantes

Mais issues de Perl

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.