-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Add trace event control for ORT Web performance profiling #23393
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
Conversation
@microsoft-github-policy-service agree company="Intel" |
@Honry Please help review this PR, thanks~ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fs-eire, please help review the type script files. Thanks!
The CI is failing and need to fix the linter error |
Thanks for the review, js format issue has been fixed, please help review again. |
@fs-eire It seems the Lint check failed in CI, and there is no specific error hint in the log. I have run "npm run format; npm run lint; lintrunner -a" commands in local to check the javascript and C++ code, and there is no error in my local check. Are there any other format rule we need to follow? Is there any guide for this? |
@fs-eire Rebase the branch and update the lint format check, please help review, thanks~ |
/azp run Windows ARM64 QNN CI Pipeline,Windows x64 QNN CI Pipeline,Windows GPU Doc Gen CI Pipeline,ONNX Runtime Web CI Pipeline,Win_TRT_Minimal_CUDA_Test_CI,Linux CPU CI Pipeline,Linux CPU Minimal Build E2E CI Pipeline,Linux GPU CI Pipeline,Linux GPU TensorRT CI Pipeline,Linux OpenVINO CI Pipeline |
/azp run Linux QNN CI Pipeline,onnxruntime-binary-size-checks-ci-pipeline,Big Models,Linux Android Emulator QNN CI Pipeline,Android CI Pipeline,iOS CI Pipeline,ONNX Runtime React Native CI Pipeline,Linux DNNL CI Pipeline,Linux MIGraphX CI Pipeline,Linux ROCm CI Pipeline |
Azure Pipelines successfully started running 4 pipeline(s). |
Azure Pipelines successfully started running 6 pipeline(s). |
@fs-eire I checked the failed CI cases, it seems not relate to this PR, do we need to retrigger the CI? |
I checked the failed jobs. The failures are not related so it’s safe to merge. |
Description
Add trace event control to better profile ORT web performance
Motivation and Context
ORT Web's current tracing implementation lacks interfaces for performance profiling using about://tracing. This PR introduces these interfaces, enabling performance bottleneck identification in ORT Web and adding several trace events for WebNN.