polikimre wrote:While the sample set is loading start task manager and go into the Resource monitor. See the load on your CPUs, the read rate from your hard drives, and compare these to the figures listed for your equipment. That will give you the bottleneck.
In most cases the bottleneck is the hard drive, followed by the CPU, as the caching of sets is not fully optimized for multiple threads (maybe only up to 4?, I don't remember exactly).
IMHO a good point to follow... but for solid decision where to locate and tackle the bottleneck the workload of the HD should be evaluated in relation to the number of tasks processed.
Roughly I found two different statesof the system over the timeline:
- a warm-up period of about 5-10 min. A huge number of processes are started. Loading samples ( not the HW prorgam) of whatever size becomes a test of ones patience.
- a waiting-for-action period. A process is started now and then.The loading of samples is fast.
An evaluation of this result opens roughly three options for a solution:
- a faster HD...but what will be its job when the loading is done, which is a very short, almost neglictable period in comparison to the time when the organ is played and there is no need for a HD at all,
- reduce the "warm-up" processes to a minimum...which, if done in a moderate way can help within limits , but may end in difficulties, if done the severe way
- live with the "warm-up" period and make use of it: dry agility exercises ( as in former times prof-pianists did with their "silent piano" ), concentrate on the music...
The decision: for me a matter of personal preferences and budget...
Amun