# Recommendation for a large library

**URL:** <https://community.roonlabs.com/t/recommendation-for-a-large-library/166947>\
**Category:** Roon Software Discussion\
**Created:** [July 29, 2021, 9:28am UTC](https://community.roonlabs.com/t/recommendation-for-a-large-library/166947 "2021-07-29T09:28:39Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![shinyc](https://community.roonlabs.com/letter_avatar/shinyc/32/5_5575768a8748004e209b776fc1b2916d.png) [@shinyc](https://community.roonlabs.com/u/shinyc)\
**Post date:** [July 31, 2021, 3:29pm UTC](https://community.roonlabs.com/t/recommendation-for-a-large-library/166947/13 "2021-07-31T15:29:46Z")

</div>

I think it is a lot more involved issue than just hardware horsepower. You might want to take a look at the following discussion:

> [@My experiences with Rock and a 500k+ tracks library](https://community.roonlabs.com/t/my-experiences-with-rock-and-a-500k-tracks-library/27385/24):
>
> Maximum single-threaded speed in the core is the main determinant in user experience snappiness. Multiple cores helps with running more zones in parallel with more DSP and will complete stuff like audio analysis faster. I wouldn’t go beneath 4 cores/8 threads for this use case. You could do more, but added value will diminish depending on how much you value those aspects. I understand the preference for Linux (and wouldn’t want to run Windows if I could avoid it), but in your shoes I’d do an A…

---

_[View the full topic](https://community.roonlabs.com/t/recommendation-for-a-large-library/166947)._
