Add ArrayContainer array operation tests and container benchmarks #11
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
Spoiler alert: After multiple cycles of attempts to apply vectorization, it seem not to breeze in more speed, at best stays on same level: | OrScalar | 1000 | 34.62 ms | It seem the reason is - vectorization shines out on large data scales (aka slow-start), while current use-case is pushed-to-the-ground (finite data). That is why this PR is only about setting the base line. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The goal is to draw a base line for these ops. Despite vectorization seem possible, it may not be worth it since arrays might be too small.
These tests will be a base line for us to measure.
Local (dev) machine results:
BenchmarkDotNet v0.14.0, Windows 11 (10.0.26100.4652)
AMD Ryzen 7 6800H with Radeon Graphics, 1 CPU, 16 logical and 8 physical cores
.NET SDK 9.0.200
[Host] : .NET 8.0.13 (8.0.1325.6609), X64 RyuJIT AVX2
DefaultJob : .NET 8.0.13 (8.0.1325.6609), X64 RyuJIT AVX2
Monster dev machine:
BenchmarkDotNet v0.14.0, Windows 10 (10.0.19045.6093/22H2/2022Update)
AMD Ryzen 9 3900XT, 1 CPU, 24 logical and 12 physical cores
.NET SDK 9.0.100
[Host] : .NET 8.0.7 (8.0.724.31311), X64 RyuJIT AVX2
DefaultJob : .NET 8.0.7 (8.0.724.31311), X64 RyuJIT AVX2
Moster should be ~10% faster for single-core ops & have ~10 % better memory -> only 'AND & XOr' are affected:
https://cpu.userbenchmark.com/Compare/AMD-Ryzen-9-3900XT-vs-AMD-Ryzen-7-6800H/m1202614vsm1786492