Conversation
…h new stricter format
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Goal is2 tracks:
1- leverage cuCIM recently added support for batch reads (rapidsai/cucim#1007)
2- use super tiles to read larger regions that then get sliced in smaller tiles to reduce number of reads
First few benchmarking runs suggest:
1- cuCIM batch read alone already provides a ~3x speed up
2- using super tiles alone can yield a ~4x speed up (but depends on whether we can find super tiles, and if so, how many we find ; so results may vary from no speed up to even higher speed up depending on the slide geometry)
3- combining both naturally yields an even higher ~12x speed up