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

Memory usage after calling actor.slicer #711

Open
ckolluru opened this issue Nov 23, 2022 · 1 comment
Open

Memory usage after calling actor.slicer #711

ckolluru opened this issue Nov 23, 2022 · 1 comment

Comments

@ckolluru
Copy link

Hi,

I have a 3D dataset (4000, 3000, 100) that I'm rendering with fury. The size of the dataset is about 1.2 GB.

When I call the actor.slicer function as: image_actor_z = actor.slicer(volume, affine), the memory usage after the call increases by approximately 6 GB.

Is this expected? I'm trying to use fury to eventually render datasets of size 50-60 GB on a workstation with 128 GB of RAM, so would this be possible? It seems not if the memory usage scales linearly with dataset size.

I tried debugging through the actor.slicer function and found that memory usage changed significantly at the following lines in actor.py. Any help would be appreciated.

Line 89: Increased by 1.2 GB vol = data
Line 91: Decreased by 1.2 GB im = ImageData()
Line 110: Increased by 1.1 GB vol = np.ascontiguousarray(vol)
Line 138: Increased by 1.1 GB image_resliced.AutoCropOn()
Line 256: Increased by 3.5 GB plane_colors.Update()

Thanks,
Chaitanya

@skoudoro
Copy link
Contributor

Thank you for the feedback @ckolluru.

We are implementing new way to handle this and improve performance. it might be present on the future release this year

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

No branches or pull requests

2 participants