IntersectMBO/plutus

Add benchmarks for compilation

Open

Aperta il 24 mag 2024

Vedi su GitHub
 (2 commenti) (0 reazioni) (0 assegnatari)Haskell (1637 star) (511 fork)batch import
BenchmarksGood first issueLow prioritystatus: triaged

Descrizione

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.

Guida contributor

Tech stack
Nessuno
Dominio
performancetesting
Tipo issue
feature
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-2 days
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
fresh
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
clear
Prerequisiti
Familiarity with Plutus compiler internalsKnowledge of Haskell benchmarking toolsUnderstanding of PIR and UPLC compilation steps
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
40
Direzione di ricerca
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.