by Lowlander » Tue Dec 27, 2016 2:53 pm
The larger the amount of the files the slower the performance will be, this is logical as more data needs to be processed. So with large Libraries somewhat speedier hardware would be wise.
It also depends on what you're doing and what other things you've done in the database. For example complex AutoPlaylists will slow any operation down that involves AutoPlaylist reading. A larger Library only makes this more pronounced.
However there are things you can do to maintain performance. Run File > Maintain Library with complete optimization on a regular basis. Make sure the database file (MM.DB) itself is defragmented on a regular HDD (non SSD) on a regular basis (Defraggler can do this for one file).
The larger the amount of the files the slower the performance will be, this is logical as more data needs to be processed. So with large Libraries somewhat speedier hardware would be wise.
It also depends on what you're doing and what other things you've done in the database. For example complex AutoPlaylists will slow any operation down that involves AutoPlaylist reading. A larger Library only makes this more pronounced.
However there are things you can do to maintain performance. Run File > Maintain Library with complete optimization on a regular basis. Make sure the database file (MM.DB) itself is defragmented on a regular HDD (non SSD) on a regular basis (Defraggler can do this for one file).