-
Notifications
You must be signed in to change notification settings - Fork 185
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
Enable DYNAMIC_CPU_ARCH in ONNXRuntime to use up to AVX2 #6855
Conversation
Enable dynamic_arch in ONNXRuntime to use up to AVX2
A new Pull Request was created by @hqucms (Huilin Qu) for branch IB/CMSSW_12_0_X/master. @cmsbuild, @smuzaffar, @mrodozov can you please review it and eventually sign? Thanks. |
@cmsbuild please test |
abort test |
enable profiling |
@cmsbuild please test |
@hqucms , have you tested locally by setting |
@smuzaffar Yes -- this is a runtime flag and onnxruntime does not need to be re-built. Basically onnxruntime detects at runtime the cpu flags and will load specific kernels if avx/avx2/avx512 are available (https://github.com/cms-externals/onnxruntime/blob/cms/v1.7.2/onnxruntime/core/mlas/lib/platform.cpp#L178). |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-85141b/14674/summary.html Comparison SummarySummary:
|
I can't find the timing piecharts in the profiling results. @gartung |
Click on "see logs" links next to profiling results. |
I thought I have FasterTimer service enabled for PR profiling. I will have to check the PR profiling job for failures. |
The PR profiling job was missing a parameter/environment variable which is checked by the profiling script before using the FastTimeService python wrapper script that enables the json output. |
Thank you. |
assign reconstruction |
+reconstruction based on #6855 (comment) |
+externals |
This pull request is fully signed and it will be integrated in one of the next IB/CMSSW_12_0_X/master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
@gartung @smuzaffar |
Right now the workflows are read from a file |
sounds good @gartung . You should also update https://github.com/cms-sw/cms-bot/blob/master/process_pr.py#L57 to support workflow_profiling |
So that maps to the variable MATRIX_EXTRAS? |
I need to add PROFILING here so MATRIX_EXTRAS_PROFILING is defined |
test parameters: |
I do not think that this will work without merging the cms-bot PR. Strange that bot did not reject your |
I was setting up this PR to test the cms-bot PR. |
please test with cms-sw/cms-bot#1545 |
abort |
As discussed in cms-sw/cmssw#32883 (comment), we would like to test the dynamic arch option in ONNXRuntime. The
MLAS_DYNAMIC_CPU_ARCH
is changed from 0 (no dynamic arch) to 2 (dynamic arch, use up to AVX2).