# 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:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@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")

</div>

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.

---

_[View the full topic](https://discourse.slicer.org/t/loading-in-huge-data/14760)._