Skip to content

[Nightly] Set different time measure for microbench #1915

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

Open
wants to merge 14 commits into
base: main
Choose a base branch
from

Conversation

RUIJIEZHONG66166
Copy link
Contributor

Enhance the op microbench test with device, test method and iter number ondemanded control.

@RUIJIEZHONG66166 RUIJIEZHONG66166 force-pushed the ruijie/set_different_time_measure branch from 13faaf7 to eda75dd Compare August 13, 2025 01:36
@RUIJIEZHONG66166 RUIJIEZHONG66166 force-pushed the ruijie/set_different_time_measure branch from 3a723b6 to 618e946 Compare August 14, 2025 06:47
@RUIJIEZHONG66166
Copy link
Contributor Author

RUIJIEZHONG66166 commented Aug 18, 2025

Ondemand test results: https://github.com/intel/torch-xpu-ops/actions/runs/16987046730
If Profile Change = "↓" or "↑", it means the regression or improvement exceed the threshold; if no Profile Change, it means the regression or improvement do not exceed the threshold.
Some outlier like case in scan.cumsum have regression because it compared with main branch results, and main branch's test scripts "scan.cumsum.py" has type issues which fixed by this PR. Will refresh the baseline after this pr merged.

@RUIJIEZHONG66166 RUIJIEZHONG66166 requested review from chuanqi129 and removed request for chuanqi129 August 18, 2025 08:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant