IntersectMBO/plutus

Add benchmarks for compilation

Open

#6,113 opened on May 24, 2024

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Haskell (511 forks)batch import
BenchmarksGood first issueLow prioritystatus: triaged

Repository metrics

Stars
 (1,637 stars)
PR merge metrics
 (Avg merge 6d 1h) (15 merged PRs in 30d)

Description

We don’t currently have any benchmarks for the compiler. It would be good to have some. We do want them to run on substantial programs, though, so ideally something that comes out of the plugin.

Fortunately, the plugin saves the (slightly-processed) PIR as well as the final UPLC, so we can do this: get a bunch of programs using the plugin, extract the PIR at runtime and then compile it in the benchmark.

Contributor guide

Research direction
Identify the plugin code that saves PIR and UPLC. Write code to extract PIR at runtime and compile it using the compiler's existing compilation functions. Use a benchmarking framework like criterion to measure compilation time. Find a set of substantial Plutus programs from the plugin's test suite or examples. Ensure benchmarks are reproducible and documented.
Tech stack
None
Domain
performancetesting
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Familiarity with Plutus compiler internalsKnowledge of Haskell benchmarking toolsUnderstanding of PIR and UPLC compilation steps
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40