Feature Overview
Image playback causes significant memory load both on the backend and frontend.
In the backend, playing generated images results in high memory usage.
In the frontend, all images are loaded at once and stored in state, which can lead to unnecessary memory consumption.
Efficient memory management is needed across the system.
Action Item: Investigate memory usage during playback and improve both backend and frontend memory handling.
Libraries and Data Handling
- Frontend: Uses Plotly for visualization.
- Backend: Uses
tifffile.imread for image loading, which loads entire images into memory.
- Action Item: Evaluate lazy-loading and chunked data access libraries such as
zarr, dask, or rasterio.
- Frontend Action: Implement logic to fetch only necessary frames based on index.
Additional References
📄 Workflow Memory Optimization Doc
Goal
Compare memory usage between the current implementation and the previous optinist version.
Feature Overview
Image playback causes significant memory load both on the backend and frontend.
In the backend, playing generated images results in high memory usage.
In the frontend, all images are loaded at once and stored in state, which can lead to unnecessary memory consumption.
Efficient memory management is needed across the system.
Action Item: Investigate memory usage during playback and improve both backend and frontend memory handling.
Libraries and Data Handling
tifffile.imreadfor image loading, which loads entire images into memory.zarr,dask, orrasterio.Additional References
📄 Workflow Memory Optimization Doc
Goal
Compare memory usage between the current implementation and the previous
optinistversion.