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.

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

Comparing Mutator Performance in CI #119

Closed
qinsoon opened this issue Jul 24, 2020 · 2 comments
Closed

Comparing Mutator Performance in CI #119

qinsoon opened this issue Jul 24, 2020 · 2 comments
Assignees
Labels
A-ops Area: Operations (e.g. CI) C-feature Category: Feature P-high Priority: High. A high-priority issue should be fixed as soon as possible.
Milestone

Comments

@qinsoon
Copy link
Member

qinsoon commented Jul 24, 2020

We would like to track the mutator performance among MMTk-NoGC, MMTk-SemiSpace, OpenJDK-epsilon and OpenJDK-G1.
This should run for every new commit in the master branch of mmtk-core (similar to perf-regression-ci).

@qinsoon qinsoon self-assigned this Jul 24, 2020
@qinsoon qinsoon added A-ops Area: Operations (e.g. CI) C-feature Category: Feature labels Jul 24, 2020
@qinsoon qinsoon added this to the v0.1 milestone Jul 24, 2020
@qinsoon qinsoon added the P-high Priority: High. A high-priority issue should be fixed as soon as possible. label Jul 24, 2020
@qinsoon
Copy link
Member Author

qinsoon commented Jul 24, 2020

This is currently blocked by #37, as we cannot get mutator performance data.

@qinsoon
Copy link
Member Author

qinsoon commented Aug 6, 2020

PR #122 and #123 added a mutator performance measurement in CI. This issue can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-ops Area: Operations (e.g. CI) C-feature Category: Feature P-high Priority: High. A high-priority issue should be fixed as soon as possible.
Projects
None yet
Development

No branches or pull requests

1 participant