Improve the performance of at and set, add Mat.atU8, Mat.setU8, etc. #58
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Releated:
simple perf test:
Maybe faster with Native Assets:
at: Mat.atU8, Mat.atI8, Mat.atU16, Mat.atI16, Mat.atI32, Mat.atF32, Mat.atF64
set: Mat.setU8, Mat.setI8, Mat.setU16, Mat.setI16, Mat.setI32, Mat.setF32, Mat.setF64
Mat.set support native types, e.g., Mat.set<cv.U8>()
In previous version, determine the Mat type is very expensive, but considering the mat type may change after creation, so it has to be get from native pointer, which costs lots of time, so for performance sensitive occasions, use atU8/setU8-like API.