Track benchmarks over time in CI

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

Mantenedores costumam responder em até 3 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
18/100
Tipo de issue
Funcionalidade
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
github-actions, python, rust
Domínio
ci-cd, performance

Direção de pesquisa

This is a design proposal, not a task yet. Start with the benchmark results table and CSV output in _bench.py, which the issue says already record step times and errors against JAX, and with the performance targets on #285. The first decision is which tool to adopt (pytest-benchmark, criterion.rs, github-action-benchmark, codspeed or bencher) and how much noise the thresholds must tolerate. Done would mean an agreed plan from a maintainer, then a first CI job that records one benchmark over time.

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

Descrição

enhancement ml

🌀 Claude: The ML demos' numbers are measured by hand and posted on #285, with the CPU and versions. Nothing records them over time, so a regression in xarray-sql, ddx, einfold or DataFusion shows up only when someone measures again.

Proposal: track benchmarks over time in CI, starting small:

  • pytest-benchmark for the Python benchmarks, including the ML demos at fixed sizes. Each step's time and its error against JAX are already in _bench.py's results table and CSV.
  • criterion.rs where the Rust code needs it.
  • github-action-benchmark to store the history and flag a regression on a PR.

Hosted runners vary from run to run, so the thresholds need to allow for that noise. Alternatives: codspeed.io, which counts instructions rather than measuring time, and bencher.dev. Both are free for open source today, but carry the risk of a SaaS changing its terms. asv is a reference for what a full history and dashboard could look like.

Raised in review of #269. The performance targets themselves are tracked on #285.

Linguagem predominante
Python
Estrelas
142
Forks
19
Merge médio
3d 47min
PRs com merge (30d)
8

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 xqlsystems/xarray-sql

Todas as issues de xqlsystems/xarray-sql

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

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