bmeurer/ivy-perf — explained in plain English
Analysis updated 2026-07-18 · repo last pushed 2019-03-19
Run the app locally to measure Angular Ivy compiler rendering performance.
Verify whether a change to Angular's compiler actually improves speed.
Use it as a reference benchmarking setup for framework-level performance testing.
Study how an Angular CLI-scaffolded project is structured for benchmarking purposes.
| bmeurer/ivy-perf | 0xradioac7iv/tempfs | 7vignesh/pgpulse | |
|---|---|---|---|
| Stars | — | 0 | 0 |
| Language | TypeScript | TypeScript | TypeScript |
| Last pushed | 2019-03-19 | — | — |
| Maintenance | Dormant | — | — |
| Setup difficulty | moderate | moderate | moderate |
| Complexity | 3/5 | 3/5 | 4/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Standard Angular CLI project, README is minimal so specifics of what's benchmarked require reading the code.
This is a performance testing project built with Angular, a web application framework. The repository appears to be a benchmarking tool created to measure how fast Angular's Ivy compiler (a rendering engine that powers modern Angular apps) performs under various conditions. The project is set up as a standard Angular application. You can run it locally on your computer to see it in action, and it includes the typical tools you'd expect: a development server for testing changes in real-time, a build system to package everything for deployment, and automated tests to verify nothing breaks. The README suggests this was scaffolded using Angular CLI, which is the official tooling that Angular developers use to create and manage projects. Who would use this? Primarily Angular developers and the Angular team itself, people building web applications and wanting to understand whether changes to the compiler or framework are making things faster or slower. If you've made an optimization to Angular's code, you'd run this project to measure whether it actually improved performance. It's the kind of tool that sits behind the scenes, helping framework maintainers make data-driven decisions about their codebase. The README is minimal and generic, suggesting this is either a work-in-progress or the real documentation lives elsewhere. For someone looking to contribute or understand the specifics of what's being benchmarked, you'd likely need to explore the actual code files rather than rely on these instructions.
A benchmarking Angular app used to measure how fast Angular's Ivy rendering compiler performs under different conditions.
Mainly TypeScript. The stack also includes TypeScript, Angular, Angular CLI.
Dormant — no commits in 2+ years (last push 2019-03-19).
License is not stated in the available content.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.