Test images with different utilization #33
Merged
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.
Enhance createTestImage to create image with configurable utilization and add 2 additional test:
0% utilization - this the best case when all work can be eliminated without reading any cluster from storage.
100% utilization - this is the worst case for both compressed and uncompressed images, when we have to read and decompress all clusters.
The test reveals that we have 2 issues:
Reading empty uncompressed image is almost 3 times slower compare to reading fully allocated image (3430 MB/s vs 8783 MB/s). Even with the inefficient io.Reader interface, we except to perform zero read many times faster compared with reading actual cluster from storage.
Decompression is extremely slow (39.28 MB/s for fully allocated image).
Example run: