Imread performance: reduced overhead of pim.open calls when reading from image sequence #182
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.
As reported by #181 the performance of
dask_image.imread
is bad in the case of reading from many input files. Also related are #121 #161.One problem with the current implementation that I noticed is that when calling
dask_image.imread.imread
with a file pattern such asim_*.tif
, for each tile that is loadedpims.open
is called on the entire file pattern. This then leads to many unnecessary instantiations ofpims.ImageSequenceND
s producing a large overhead.In this proposed fix I use glob to match filenames and frames to call
pims.open
only on the files that are actually being loaded.