osteele / osteele/liquid

Maintain benchmark suite and publish reproducible comparisons

Open
#32 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

help wanted research
Dominant language
Go
Stars
354
Forks
72
PR merge metrics
No merged PRs in 30d

Description

Current status

The repository now has Go benchmarks for parsing, rendering, drops, expressions, and filters. The stale engine benchmark templates were repaired in #148, and the full suite executes with:

cgo-test -run "^$" -bench . ./...

This issue remains open for turning those benchmarks into a maintained, useful performance suite.

Remaining work

  • Select representative fixtures for parsing and rendering rather than relying only on small synthetic templates.
  • Add a fast CI smoke check that compiles and executes each benchmark once, without treating noisy timing changes as regressions.
  • Document reproducible local benchmark commands, including benchstat comparisons.
  • Record Go version, OS, CPU, benchmark count, and dependency versions with published results.
  • Evaluate cross-engine comparisons against current Liquid implementations using equivalent fixtures and clearly documented semantics.
  • Keep performance claims separate from correctness and compatibility claims.

References

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running cgo-test -run "^$" -bench . ./... to inspect the existing Go benchmark suite, then review the referenced comparison projects and remaining-work list. Done means representative fixtures, a non-regression CI smoke check, reproducible benchmark documentation, recorded environment metadata, and clearly scoped cross-engine comparisons.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
performance, testing, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.