Uh oh!
There was an error while loading. Please reload this page.
Changes some of the CPU Math implemenation from our current version to use the new TensorPrimitives package. - #6875
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Codecov Report
Additional details and impacted files@@ Coverage Diff @@## main #6875 +/- ##
==========================================
- Coverage 69.40% 68.80% -0.60%
==========================================
Files 1238 1240 +2 Lines 249462 249392 -70 Branches 25522 25493 -29 ==========================================
- Hits 173139 171599 -1540 - Misses 69578 71196 +1618 + Partials 6745 6597 -148
Flags with carried forward coverage won't be shown. Click here to find out more.
|
michaelgsharp
commented
Nov 14, 2023
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
Uh oh!
There was an error while loading. Please reload this page.
This changes some of the CPU Math implementation from our current version to use the new TensorPrimitives package.
Currently we are pointing to the rc2 version, but the following benchmarks have been done with a local copy of the GA version.
This also changes CPUMath to target .NET 8 instead of .NET 6. Did we want that for this version? Or should I change it back to 6 for this release? @ericstj@jeffhandley
The following is a summary of the methods in CPUMath, the old vs new benchmarks, and whether I updated it to use the new TensorPrimitives package. @tannergooding@stephentoub@jeffhandley@ericstj@luisquintanilla This is where we need to discuss. Is any performance hit worth taking? Or should anything that is slower be kept on the existing code?
NET 8
Framework
I think that even if we don't want to keep the TensorPrimitives code in the cases where its slower, at least for .NET Framework we should add a check and if the native code doesn't exist to run these accelerated, we should fallback to the TensorPrimitives approach. That would have to be added in though.
All this was done with AVX256.