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

CI shows a strange 12% slowdown for JikesRVM/SemiSpace/lusearch #341

Open
qinsoon opened this issue Jun 7, 2021 · 0 comments
Open

CI shows a strange 12% slowdown for JikesRVM/SemiSpace/lusearch #341

qinsoon opened this issue Jun 7, 2021 · 0 comments
Labels
F-investigate Call For Participation: Investigate the issue and provide more detailed direction P-high Priority: High. A high-priority issue should be fixed as soon as possible.

Comments

@qinsoon
Copy link
Member

qinsoon commented Jun 7, 2021

Starting from this PR #324, we sometimes observed our CI shows a 12% slowdown when comparing a PR with master for JikesRVM/SemiSpace/lusearch. We also observed this slowdown in a few PRs after that (for example: #334 (comment)). This slowdown randomly happens (sometimes we do not see the slowdown). If we see the slowdown, it always shows ~12% slowdown for a PR comparing with master for that one benchmark. In such case, the result for the master is strangely faster (~580ms) which normally should be around 610-620ms.

https://www.mmtk.io/ci-perf-result/master/jikesrvm_semispace_history.html shows that from the run 2021-04-19-Mon-161118, our results for lusearch starts to have a large variance that matches the slowdown we observed. We should investigate further into this.
The PRs that were merged before the run 2021-04-19-Mon-161118 are:

We should investigate further into this.

@qinsoon qinsoon added the F-investigate Call For Participation: Investigate the issue and provide more detailed direction label Jun 7, 2021
@udesou udesou added the P-high Priority: High. A high-priority issue should be fixed as soon as possible. label Dec 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
F-investigate Call For Participation: Investigate the issue and provide more detailed direction P-high Priority: High. A high-priority issue should be fixed as soon as possible.
Projects
None yet
Development

No branches or pull requests

2 participants