| just slapping in lots of lovely memory into a machine
sounds good in concept.
but, as always there are subtle aspects to be aware of.
there is never a free lunch.
in some cases adding too much memory can in fact impede
performance.
think of it like this. conceptually.
you have 5 friends in your lounge, you tend the bar and can easily
keep track of where everyone is n keep em happy.
now put 1000 friends in that same room n ya can get frazzled trying to
keep everyone happy n serviced with drinks.
(think of the OS as the bar tender. n the sample memory as friends.)
with computers there is often a memory "sweet spot".
in some respects memory speed is a limitation.
specialised monitoring software should be able to tell you
at what point adding more memory might impede performance.
cos as you ramp up the number of samples stored in mass memory ,
remember there is overhead (like the friends in your lounge.)
in keeping track of where everything is located.
ie..the application itself has more overhead dealing with 1000
samples than 5 samples.
what i would prolly do as a test also is load a few samples.
get the tracks recorded right n stored on disc.
before exiting the daw application look at an activity monitor.
then exit the application , look at the activity monitor again n
make sure memory had in fact been released back into the memory pool as it were.
then go back in again n do a few more tracks etc etc.
if you do enough testing prolly youll find i suspect a sweet spot
of number of samples loaded vs performance.
i suspect in some cases loading up a big gob of samples into a big gob of memory
can lead to performance stifling in other areas.
mebe other applications/processes/tasks are thus impacted.
thus leading to panics. |