# Can Slicer utilise multiple cores on linux?

**URL:** <https://discourse.slicer.org/t/can-slicer-utilise-multiple-cores-on-linux/9240>\
**Category:** Support\
**Created:** [November 21, 2019, 10:23am UTC](https://discourse.slicer.org/t/can-slicer-utilise-multiple-cores-on-linux/9240 "2019-11-21T10:23:20Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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 21, 2019, 9:52pm UTC](https://discourse.slicer.org/t/can-slicer-utilise-multiple-cores-on-linux/9240/6 "2019-11-21T21:52:39Z")

</div>

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/can-slicer-utilise-multiple-cores-on-linux/9240)._