-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Add perf tests for Blob storage scenarios. #17897
Add perf tests for Blob storage scenarios. #17897
Conversation
Create stand-alone test apps for Azure.Storage.Blobs and Microsoft.Azure.Storage.Blob
...rage/Azure.Storage.Blobs/perf/Azure.Storage.Blobs.Perf/Infrastructure/PerfStressTransport.cs
Outdated
Show resolved
Hide resolved
.../Azure.Storage.Blobs/perf/Microsoft.Azure.Storage.Blob.Perf/Infrastructure/RandomBlobTest.cs
Outdated
Show resolved
Hide resolved
sdk/storage/Azure.Storage.Blobs/perf/Microsoft.Azure.Storage.Blob.Perf/Scenarios/UploadBlob.cs
Outdated
Show resolved
Hide resolved
Reuse stream where possible.
These elements are just fine on their own, but this places current and legacy perf tests side-by-side when there are no controls into the parallelism of individual methods. It probably won't make a difference for testing small files, but when testing files that the SDKs partition for upload/download, they choose very different parallelism values by default; current chooses 2 and legacy chooses a function of logical cores on the machine. Unless we truly just want to compare defaults, which we could "fix" by just bumping the default core count for the current SDK, I worry the results generated by this code will lead us to wrong conclusions when comparing the different storage SDKs. |
The 2 tests are supposed to be run independently with individual controls of the degree of parallelism, load size and other tweakable parameters. |
* Add perf tests for Blob storage scenarios. Create stand-alone test apps for Azure.Storage.Blobs and Microsoft.Azure.Storage.Blob
Create stand-alone test apps for Azure.Storage.Blobs and Microsoft.Azure.Storage.Blob