# Loading in huge data
**URL:** https://discourse.slicer.org/t/loading-in-huge-data/14760
**Category:** Support
**Created:** [November 24, 2020, 11:05pm UTC](https://discourse.slicer.org/t/loading-in-huge-data/14760 "2020-11-24T23:05:06Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@NoobForSlicer](https://discourse.slicer.org/u/NoobForSlicer)
#### Post date: [November 24, 2020, 11:05pm UTC](https://discourse.slicer.org/t/loading-in-huge-data/14760/1 "2020-11-24T23:05:06Z")
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 friend Samsung 980 PRO PCIe 4.0 (up to 7,000 MB/s)
7000 MB/s and our boss upgraded machines to over 60GB of ram.
because what he had me working with some months ago was idk… very horrible.
With this new hardware NVMe I supposed loading in should be faster. But it isn’t. Or at least I don’t notice any change.
The speed is supposably more than 20 times faster than the old SSD.
Well… Why?
I assume there is somet recalculation that the CPU has to do and so disk speed isn’t even important that much because bottle neck is made by the CPU processing speed?
---
### Author:  [@timeanddoctor](https://discourse.slicer.org/u/timeanddoctor)
#### Post date: [November 25, 2020, 5:59am UTC](https://discourse.slicer.org/t/loading-in-huge-data/14760/2 "2020-11-25T05:59:23Z")
The script code maybe edit by python which will be blocked by the GIL：[https://realpython.com/python-gil/](https://realpython.com/python-gil/)
So the speed will not improve significantly after the update of computer if you donnot recode the script.
---
### Author:  [@muratmaga](https://discourse.slicer.org/u/muratmaga)
#### Post date: [November 25, 2020, 6:55am UTC](https://discourse.slicer.org/t/loading-in-huge-data/14760/3 "2020-11-25T06:55:41Z")
Because reading and writing thousands of files individually has a lot of overhead. See this
> [@Can Slicer utilise multiple cores on linux?](https://discourse.slicer.org/t/can-slicer-utilise-multiple-cores-on-linux/9240/6):
>
> Out of curiosity, I made a rough test. Reading a sequence of 2200 PNG images that resulted in a 10GB volume took 3’ 25" on a 32GB laptop with a nvme drive (Using ImageStack from @pieper). Saving same volume as nrrd without compression took about 4 seconds. Flushing the cache and reloading the uncompressed 10GB NRRD into a fresh instance of Slicer took 26 seconds.
---
### Author:  [@NoobForSlicer](https://discourse.slicer.org/u/NoobForSlicer)
#### Post date: [November 25, 2020, 3:05pm UTC](https://discourse.slicer.org/t/loading-in-huge-data/14760/4 "2020-11-25T15:05:36Z")
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.