=== Running Benchmarks (please do not interrupt) ===
Running 'Math' benchmark...
Single-threaded integer math... 3.629 seconds
Single-threaded floating point math... 2.216 seconds
Multi-threaded integer math... 1.084 seconds
Multi-threaded mixed math... 0.661 seconds
Score: 2503
Running 'Image' benchmark...
Image creation / destruction... 0.137 seconds
Flood filling... 0.296 seconds
Direct copying... 0.303 seconds
Small renders... 0.992 seconds
Bilinear rendering... 0.764 seconds
Bicubic rendering... 0.400 seconds
Score: 7607
Running 'Database' benchmark...
Create database... 0.169 seconds
Populate database... 0.816 seconds
Save database... 0.100 seconds
Reload database... 0.025 seconds
Search database... 0.757 seconds
Sort database... 0.665 seconds
Group database... 0.520 seconds
Score: 7045
JRMark (version 20.0.47): 5718
Are these acceptable specs to deal with a library of over 500k tracks?
With iTunes once I hit around 200, it was nearly unusable.
Not that I have 500k tracks but I might get another drive in with around 150k tracks on it from a friend and so just curious how it would deal.