> well, all in all the database reacts very fast, that's for sure. But it
> depends on the hardware. Having a really big library (mine has about
> 400.000 titles, running on a rasberry pi 3 with a locally attached 4Tb
Wow... that's a lot of title for the little device! Would be interesting
to see how it behaved with a Pi4 + more RAM. Where does the cache folder
live?
Did you set the database memory setting to "maximum" in
Settings/Advanced/Performance? Somewhere beyond 50k tracks this becomes
crucial. But I can't guarantee it would work with "only" 1GB of memory...
--
Michael
> depends on the hardware. Having a really big library (mine has about
> 400.000 titles, running on a rasberry pi 3 with a locally attached 4Tb
Wow... that's a lot of title for the little device! Would be interesting
to see how it behaved with a Pi4 + more RAM. Where does the cache folder
live?
Did you set the database memory setting to "maximum" in
Settings/Advanced/Performance? Somewhere beyond 50k tracks this becomes
crucial. But I can't guarantee it would work with "only" 1GB of memory...
--
Michael