So one man from here called Alex_Vergara helped me process huge batches of .png images. He made an incredibly well script module but I have some questions concerning Slicer in general. I noticed once a batch of PNG images is being loaded in, it is not the disk speed that matters. I got NVMe from a…

The script code maybe edit by python which will be blocked by the GIL： https://realpython.com/python-gil/ So the speed will not improve significantly after the update of computer if you donnot recode the script.

Because reading and writing thousands of files individually has a lot of overhead. See this [image] Can Slicer utilise multiple cores on linux? Support Out of curiosity, I made a rough test. Reading a sequence of 2200 PNG images that resulted in a 10GB volume took 3’ 25" …

incredible post, I became interested because yesterday they gave me over 60 GB of png sequence. with 60gb ram and 1000 GB NVMe available for virtual ram memory and storing images, it worked fine and everything is okay.

Loading in huge data

Support

muratmaga (Murat Maga) November 25, 2020, 6:55am 3

Because reading and writing thousands of files individually has a lot of overhead. See this

Topic		Replies	Views
NVMe instead of RAM for Slicer? Support	4	272	October 27, 2020
Can Slicer utilise multiple cores on linux? Support	5	914	November 21, 2019
Long delay after disk activity stops when loading very large data Support	13	558	December 16, 2021
Slicer becomes slower over time during surgical navigation cases Support	7	465	April 20, 2022
loading a huge amount of data Support	0	213	March 10, 2020

Loading in huge data

Related topics