Page 1 of 1

More DP9 "Processing" status talk....

Posted: Thu Nov 12, 2015 9:20 am
by Topo
Now that I've had my iMac upgraded with an SSD and a SATA port, as well as additional RAM to 16GB, I am wondering if I need to further optimize performance, by going for the 32GB of RAM. As I have just started bringing my system back up with all the new software installs, I have not done any audio recording...just added 3 different VI's. In my quick tests, I see the "Processing" meter bouncing around 1/3 to 1/2. Is this normal (for those of you that have an i7 iMac). Would I see anything different with 32 gigs of ram? How can I actually see a performance boost with more ram. I'm trying to decide whether it's worth it to spend another $200. on RAM.

Re: More DP9 "Processing" status talk....

Posted: Thu Nov 12, 2015 9:24 am
by MIDI Life Crisis
I would add the RAM, especially if you're working with lots of audio and/or VIs.

Re: More DP9 "Processing" status talk....

Posted: Thu Nov 12, 2015 12:33 pm
by Shooshie
Check your buffer. If it's set for 64 or less, you might consider raising it to 128 or higher. Small buffers are great for eliminating latency when recording, but when running VIs and plugins a larger buffer helps the CPU dramatically.

If your buffer is already set to a high number, then I'm not sure what might be going on there. First check the buffer before we speculate on other causes.

Shooshie

Re: More DP9 "Processing" status talk....

Posted: Thu Nov 12, 2015 1:14 pm
by Topo
I might have lowered it...have to check later, but my other question is more about whether a larger amount of RAM will decrease processor load....and, if paying attention to the processing meter is really something to be paying attention to. I recall, in DP7, I had to turn off the warning that said you've exceeded the bandwidth limits of....etc, and it would shut off output thru the hardware. When I turned that off, I never had a problem....things may have been pushing the app to it's boundaries, but I never saw it degrade my projects.
Shooshie wrote:Check your buffer. If it's set for 64 or less, you might consider raising it to 128 or higher. Small buffers are great for eliminating latency when recording, but when running VIs and plugins a larger buffer helps the CPU dramatically.

If your buffer is already set to a high number, then I'm not sure what might be going on there. First check the buffer before we speculate on other causes.

Shooshie

Re: More DP9 "Processing" status talk....

Posted: Thu Nov 12, 2015 1:18 pm
by mikehalloran
I have 20G in mine because the extra two slots were a convenient place to store two of the factory 2G modules. 2x8 + 2x2. For my use, lots of audio and low - medium VI usage, 16G would probably be fine, too.

My wife's biggest RAM use is Word. I have 12G in her iMac. If I really thought I needed more, I'd swap her 4G sticks for my 2G – then I'd have 24G and she'd have 8G. I've never felt the need, however.

BTW, if you still have a couple of the OE sticks, put them in. Can't hurt. RAM must be installed in pairs, R/L. With all four slots filled, it doesn't matter which two are front and which are rear. It won't boot if you put both 8s on one side and the 2s on the other.

What Shooshie says about buffer size. I run 512 without problems but I have not tried 128 since I went to an SSD. Every once in awhile, I will work on an outside project where 1024 is a good idea to keep things flowing.

When tracking, I run 64 or 128 depending on how many previous tracks need to be playing at the same time.

Re: More DP9 "Processing" status talk....

Posted: Thu Nov 12, 2015 10:36 pm
by Shooshie
Topo wrote:I might have lowered it...have to check later, but my other question is more about whether a larger amount of RAM will decrease processor load....and, if paying attention to the processing meter is really something to be paying attention to.
Processor load is a direct product of the buffer size. No discussion about extra RAM vs. CPU load can be of any value without knowing your buffer size. It's the critical hinge upon which all CPU timing becomes relevant.

Shooshie