Skip to content
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

reader vs converted and performance #12

Closed
LucaMarconato opened this issue Jan 12, 2023 · 1 comment
Closed

reader vs converted and performance #12

LucaMarconato opened this issue Jan 12, 2023 · 1 comment

Comments

@LucaMarconato
Copy link
Member

@giovp we need to test if we can use readers (as the one in your new pr) or if we need for some large datasets to use converters. The reason is that Dask allows to represent lazily the data in both cases, but the operations with a reader could be not performant.

For example, say that you want to read a .ome.tiff file, or rotate an image. With dask-image you can have a Dask array that represents in-memory lazily both of them, construct a SpatialData object and, say, view it in napari. But the visualization will be really poor. Here what would help is to first save the object to .zarr, and then reinitialize the array to read from disk. Now the visualization will be performant.

@LucaMarconato
Copy link
Member Author

Now with scverse/spatialdata#117 when we save to disk the spatialdata object is re-read and the performance problem is addressed. We just have to make aware the user that the data should be saved to have better performance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant