Hello, thanks. I now understand better the mechanism behind it.
I m running some tests. I am loading a music instrument inside a sampler named Kontakt (standalone app). The patch I am loading weight 18 Gb. I tried to put it outside the pool, then inside the pool.
When it's inside the pool, it seems to take a bit more time to load.
Something like 0.5 sec when outside the pool, but 2 seconds when inside the pool. Is it because I am using different SSD models in my pool ?
- Samsung 980 1 tb (gen 3, Dramless) 0.5s when the library is here
- Samsung 970 Evo plus 2tb (gen 3, dram) 0.5s when the library is here
- Netac nv7000 2 tb (gen 4, dram) 0.5s when the library is here
This famous sampler have a "batch re-save" function, which basically re-save that specific library in the exact path (a little bit like indexing which make loading times super fast, and you only perform a batch re-save once per library and forget it. So there's a workaround for this, but still out of curiosity, do you have any idea why loading speed seems slower when using the pool ? Give me best guidances
THANKS