In my case, PD13 will gladly eat up almost all of my 16GB and 100% cpu (i7-4770) on the some tasks (but not all).

It's true though that at idle with a 3hr movie and 550 clips, it only commits 1.4GB I7-4770, 3.40Ghz, 16GB RAM, Asus Z87-Plus Z87chipset, Sapphire ATI Radeon HD7850 PCI Express-16 3.0 2GB, Samsung EVO 840 SSD 1TB

Quote: In my case, PD13 will gladly eat up almost all of my 16GB and 100% cpu (i7-4770) on the some tasks (but not all).

It's true though that at idle with a 3hr movie and 550 clips, it only commits 1.4GB

Oh really? Wonder if I'm doing something wrong?

Quote: In my case, PD13 will gladly eat up almost all of my 16GB and 100% cpu (i7-4770) on the some tasks (but not all).

It's true though that at idle with a 3hr movie and 550 clips, it only commits 1.4GB

CV27, post a pic of your timeline and PD13.exe using 16GB, I'd like to see that. I sure can't come close to that. OP was addressing memory during timeline scrubbing, I've never seen anything near 16GB for such activity and would welcome a pic. To my knowledge no signficant timeline section is preloaded in RAM so it's read as you scrub along the timeline.

Most memory I've seen utilized is during encoding, not timeline scrubbing. Attached are a couple of pics showing a 3x3 video wall, total of nine, 4K 59.94fps 50Mbps video files and CPU encoding thereof. Probably a significant load for any system, max memory used during 4K 50Mbps H.264 encode, 4.8GB. Again, nothing I really see in this serial encode process to be a memory hog, computationaly intensive to encode is all.

DaveImagery, what you are seeing for memory usage is typical for what I've seen with PD. If you want to speed up timeline scrubbing only real effective method I know is to create shadowfiles which is another very slow process. You turn these on in pref > General "Enable HD video processing" and then wait for the left corner of each HD clip in the library to get a green movie icon before editing. Hopefully PD14 offers some significantly improved timeline performance, long overdue.

Jeff

Quote:

Quote: In my case, PD13 will gladly eat up almost all of my 16GB and 100% cpu (i7-4770) on the some tasks (but not all).

It's true though that at idle with a 3hr movie and 550 clips, it only commits 1.4GB

CV27, post a pic of your timeline and PD13.exe using 16GB, I'd like to see that. I sure can't come close to that. OP was addressing memory during timeline scrubbing, I've never seen anything near 16GB for such activity and would welcome a pic. To my knowledge no signficant timeline section is preloaded in RAM so it's read as you scrub along the timeline.

Most memory I've seen utilized is during encoding, not timeline scrubbing. Attached are a couple of pics showing a 3x3 video wall, total of nine, 4K 59.94fps 50Mbps video files and CPU encoding thereof. Probably a significant load for any system, max memory used during 4K 50Mbps H.264 encode, 4.8GB. Again, nothing I really see in this serial encode process to be a memory hog, computationaly intensive to encode is all.

DaveImagery, what you are seeing for memory usage is typical for what I've seen with PD. If you want to speed up timeline scrubbing only real effective method I know is to create shadowfiles which is another very slow process. You turn these on in pref > General "Enable HD video processing" and then wait for the left corner of each HD clip in the library to get a green movie icon before editing. Hopefully PD14 offers some significantly improved timeline performance, long overdue.

Jeff

Thanks for all the info Jeff.

I guess I was just expecting PD13 to be using more ram than it does, since it's a 64Bit program.

Quote:
I guess I was just expecting PD13 to be using more ram than it does, since it's a 64Bit program.

A 64-bit program simply determines maximum memory space a particular application can address, if required, not that it has to use all the available RAM. How much a particular program uses depends on coding architecture of the program and what the programmers see as value added to retain in RAM.

Generally most like a frugal RAM footprint unless an advantage to use more RAM, it’s always very easy to write bloat software that uses a lot of RAM needlessly.

Jeff

Interesting. I dismantled my 2 850 Pro SSD raid 0 array, because the Crucial SSD in my wife's computer died, and I (very kindly) donated one of mine to her system.

Running PD13 again with a single drive, I'm noticing no reduction in speed when scrubbing through video. Which seems odd. You would think raid 0 would be much faster?

Also been experimenting with enabling/disabling the Samsung Rapid mode for the single drive, in which up to 2gb of my 32gb of ram is used to supposedly further speed up the system. PD13 actually seems worse, with it on.

Quote: Interesting. I dismantled my 2 850 Pro SSD raid 0 array...

Running PD13 again with a single drive, I'm noticing no reduction in speed when scrubbing through video. Which seems odd. You would think raid 0 would be much faster?
...

I'm sure you did the typical initial performance tests when you got your SSD's and found that Raid 0 had clear benefits. In real life though, as with PD13 and scrubbing, resource usage in memory and CPU are so intense that disk access becomes less visible. But Raid 0 is still a winner for disk intensive tasks (boot, program load, long copies..).

Quote: ... Also been experimenting with enabling/disabling the Samsung Rapid mode for the single drive, in which up to 2gb of my 32gb of ram is used to supposedly further speed up the system. PD13 actually seems worse, with it on.

My 850 Pro is also set up at 2GB. I was not totally impressed with the performance boost from my initial tests having it On and Off. But I sure wouldn't go back to HDD. I7-4770, 3.40Ghz, 16GB RAM, Asus Z87-Plus Z87chipset, Sapphire ATI Radeon HD7850 PCI Express-16 3.0 2GB, Samsung EVO 840 SSD 1TB

Quote:

Quote: Interesting. I dismantled my 2 850 Pro SSD raid 0 array...

Running PD13 again with a single drive, I'm noticing no reduction in speed when scrubbing through video. Which seems odd. You would think raid 0 would be much faster?
...

I'm sure you did the typical initial performance tests when you got your SSD's and found that Raid 0 had clear benefits. In real life though, as with PD13 and scrubbing, resource usage in memory and CPU are so intense that disk access becomes less visible. But Raid 0 is still a winner for disk intensive tasks (boot, program load, long copies..).

Quote: ... Also been experimenting with enabling/disabling the Samsung Rapid mode for the single drive, in which up to 2gb of my 32gb of ram is used to supposedly further speed up the system. PD13 actually seems worse, with it on.

My 850 Pro is also set up at 2GB. I was not totally impressed with the performance boost from my initial tests having it On and Off. But I sure wouldn't go back to HDD.

A little while back there was a firmware problem with my first drive, an 840 Pro. I was referred to a ssd tech at Samsung for troubleshooting. While I had him on the phone, I asked him about Rapid mode, and did it actually increase performance. His response was surprising. "In a few situations yes, but for the most part not really." Guess he didn't get the marketing memo. lol

Also discovered you can't benchmark the drive while in rapid mode. Depending on the benchmarking utility. It either won't benchmark at all, or the results will be inflated to hell. Have to disable rapid, reboot, then test it. Then re-enable rapid, and reboot. Not very convenient. I suppose there are some sort of algarhythms, which learn what programs you most frequently use, and throws them into ram, for faster loading, but I'm afraid I just don't see any real performance boost.

Next step up in performance, would be one of those sexy Intel 750 PCIE drives. 2.0Gb read/writes!