Quote:
Originally Posted by
zaphod
➡️
I understand you have a lot of RAM, but we’re not doing anything unusual on our end. I’m also not sure that all available RAM runs at the same speed—there might be differences that affect performance. Or bottlenecks. We are using standard calls
Thanks for your reply.
Yes, the RAM problem is the main issue.
I think it's a important issue to look at, because it is unified memory and how aqua's handle memory could be the bottleneck itself for loading times and GUI issues.
No one of my last 6 machines had so much RAM and the CPU's couldn't handle as much instances as a total amount of RAM over 40 GB could ever been reached.
As the slow down happens exponential, the behavior could be that way for all the time of the past.
Most important is, someone else does a stresstest with a m4 max or m3 ultra by using about 4 instances per track, duplicate it till about 45-50 GB of RAM are reached and hold an eye on loading times.
Istats or Activity Monitor ar the most accurate.
Use a modest buffersize of 1024.
I also checked if REAPER or my specific machine is the bottleneck.
In Logic Pro it's the same issue.
Using Kontakt in REAPER I could create and load projects with over 50 GB of RAM with ease and very fast.
Please, could you do a similar stresstest and report if the issue could be replicated?