Closed minhduc66532 closed 3 years ago
It is due to usage of Parallel.For internally by our DefaultEngine
, we are considering to remove this feature in favor of regular tight for-loop by default where Parallel.For will be exposed via ParallelEngine
that can be assigned to any NDArray.
Any performance impact beyond that is the overhead of creating the NDArray, allocating the memory and handling dtype
and shape behind the scenes.
Ohh ok, so more improvements coming soon I guess. Thank you for the answer
The result: Am I doing anything wrong because from the test result NumSharp is 3 times slower than normal for loop