Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Performance tracking #3299

Open
bclement-ocp opened this issue Nov 22, 2024 · 0 comments
Open

Performance tracking #3299

bclement-ocp opened this issue Nov 22, 2024 · 0 comments
Labels
flambda2 Prerequisite for, or part of, flambda2 profiling Changes to system for profiling the performance of the compiler

Comments

@bclement-ocp
Copy link
Contributor

We should have a way to track compile times and check that they do not balloon up too much.

Off the top of my head we probably want to track (and collect statistics for):

  • Compilation times of the stdlib,
  • Compilation times of the compiler,
  • Compilation times of some curated opam packages,
  • Running times of selected benchmarks

We probably don't need to run these on each PR, but it would be good to run them at least weekly.
@bclement-ocp bclement-ocp added flambda2 Prerequisite for, or part of, flambda2 profiling Changes to system for profiling the performance of the compiler labels Nov 22, 2024
This was referenced Nov 22, 2024
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
flambda2 Prerequisite for, or part of, flambda2 profiling Changes to system for profiling the performance of the compiler
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bclement-ocp