search

nuprl / Stopify

A JS-to-JS compiler that makes it easier to build Web IDEs and compile to JS.
https://zenodo.org/records/10408254
BSD 3-Clause "New" or "Revised" License
168 stars 12 forks source link

Performance testing for pull requests #373

Open rachitnigam opened 6 years ago

rachitnigam commented 6 years ago

We're making some changes to the instrumentation this summer. We should bring back performance testing for Pull requests to make sure we don't have big regressions.

We used to have a cluster for doing the performance testing. Consider bringing that back up.

arjunguha commented 6 years ago

maybe this doesn't matter. we don't need PLDI-grade performance any more. integrate with pyret and we can use pyret's performance benchmarks as a proxy.

rachitnigam commented 6 years ago

Would that work for codeHS? Isolating major performance regressions at the Stopify level would be better than using Pyret as a proxy.

To be clear, not all PRs need perf testing. We just need to maintain a baseline and test against it on every major PR (eg: stack traces, adaptive deep stacks).