# CPU Performance

**URL:** <https://uzu.lurk.org/t/cpu-performance/4008>\
**Category:** Uncategorized\
**Created:** [18 April 2022 12:46 UTC](https://uzu.lurk.org/t/cpu-performance/4008 "2022-04-18T12:46:53Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![kit-christopher](https://uzu.lurk.org/user_avatar/uzu.lurk.org/kit-christopher/32/686_2.png) [@kit-christopher](https://uzu.lurk.org/u/kit-christopher)\
**Post date:** [18 April 2022 14:35 UTC](https://uzu.lurk.org/t/cpu-performance/4008/2 "2022-04-18T14:35:23Z")

</div>

there's a great "lazy" sample loading feature you can use but now I'm not sure how much CPU it will buy you.

> [@Superdirt lazy samples loading](https://club.tidalcycles.org/t/superdirt-lazy-samples-loading/3148):
>
> Recently ([Samples lazy loading · Issue #238 · musikinformatik/SuperDirt · GitHub](https://github.com/musikinformatik/SuperDirt/issues/238)) a new feature on superdirt was implemented, it permits to avoid loading of the whole sample libraries in memory, and loading every sample the first time it's requested by your tidal code. To enable it, update superdirt to the last commit (go into the downloaded-quarks/SuperDirt folder then git pull) then, in the superdirt startup code, before any ~dirt.loadSoundFiles call, put a ~dirt.doNotReadYet = true; I'm usi…

---

_[View the full topic](https://uzu.lurk.org/t/cpu-performance/4008)._