imread - investigate possible performance improvement
See original GitHub issueIt’s been found that the performance of da.map_blocks
is much better than da.stack
when joining large arrays: https://github.com/dask/dask/issues/5913
It’s unclear if da.concatenate
(like we use in imread) is also slower, but this seems likely. We should investigate if we can get a performance benefit by switching to da.map_blocks
.
Issue Analytics
- State:
- Created 3 years ago
- Comments:16 (3 by maintainers)
Top Results From Across the Web
AttributeError: module 'cv2' has no attribute 'imread'
Reader's problem could be, that a wrong library (cv2 package) has been installed. I installed opencv-python3 instead of opencv-python for ...
Read more >Working with skimage – Image Processing with Python
Let us examine a simple Python program to load, display, ... Then, we use the iio.imread() function to read a JPEG image entitled...
Read more >Image Processing Toolbox™ User's Guide
reduced resolution data set (R-Set) can improve performance. Use the Image. Viewer to navigate an R-Set image the same way you navigate a...
Read more >Faster video file FPS with cv2.VideoCapture and OpenCV
Learn how to boost video file FPS processing throughout by over 52% utilizing threading with OpenCV and Python.
Read more >Solved [USE MATLAB] 1. Load an image “SanDiego.jpg” in to
Plot title: “original color image” Hint: imread, imshow 2. Contrast enhancement is a cool way to learn image processing. ... possible pixel values....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi guys, just saw this here and remembered that I did stumble upon bad performance of
dask.image.array.stack
in the past when creating large arrays.So I added a
da.map_blocks
version ofdask_image.imread.imread
and compared it to the current implementation usingda.concatenate
.map_blocks
implementation:Comparison:
So there’s a big performance difference!
Also, indexing the resulting array is faster in the
map_blocks
version:So it seems that
map_blocks
is the way to go for putting together large images. Happy to open a PR.Closed by https://github.com/dask/dask-image/pull/165