render very slow

[Tom Daigon]

Certainly! Glad to help.

Tom Daigon
PrP / After Effects Editor
http://www.hdshotsandcuts.com
https://www.youtube.com/watch?v=XRIg6h-LIm0 (Best viewed at 1080P and full screen)
HP Z820 Dual 2687
64GB ram
Dulce DQg2 16TB raid

[Walter Soyka]

Where is your DPX sequence located? Unless you have it on a high-performance RAID, this is almost certainly your bottleneck. A single disk cannot keep up with the data requirements for a DPX sequence, and if the computer can’t get the frames fast enough, it will never play in real time or max out the CPU.

Walter Soyka
Principal & Designer at Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog – What I’m thinking when my workstation’s thinking
Creative Cow Forum Host: Live & Stage Events

[Jim Hoyle]

Hi Felix,

Did you get the processors maxed out? Or even some performance gains? I am having a similar problem. On my previous 5 year old system, I don’t think my CPU cores or GPU load were totally maxed out in Premiere Pro CS6. However, it was basically as fast if not faster for basic conversions as my new system is. In my new system the CPU usage is really low. Both when enabling or disabling CUDA in Premiere. When disabling CUDA in Premiere, the CPU usage goes 5% up and GPU load goes to 0%, but overall the speed is pretty much the same and very slow.

I have now
– Asus P9X79 motherboard
– Intel i7-3930K processor
– 64GB mem
– one SSD drive, rest fast hard drives
– PNY Quadro FX 3800 display card

Right now I’m doing a simple conversion from ProRes .mov to VP6 .flv. It takes forever. GPU load is 22% and average CPU cores usage is somewhere around 12%.

[Jim Hoyle]

Additional information: I couldn’t see any difference by tampering some CPU settings in BIOS. Also the hard drive is definitely not the bottle neck here. Windows 7 Resource Monitor tells me “Adobe QT32 Server.exe” reads only 4MB/sec when exporting, while my drives easily easily allow read/write at least 10 times faster than that.

[Walter Soyka]

[Jim Hoyle] “Additional information: I couldn’t see any difference by tampering some CPU settings in BIOS. Also the hard drive is definitely not the bottle neck here. Windows 7 Resource Monitor tells me “Adobe QT32 Server.exe” reads only 4MB/sec when exporting, while my drives easily easily allow read/write at least 10 times faster than that.”

The hard drive may still be the bottleneck. Transfer speed is only one metric; IOPS (input/output operations per second) is another. Look at the disk tab of Resource Monitor during render. If the queue length graph is high, this means that there are many pending requests for I/O to the disk. In other words, the disk cannot fulfill discrete I/O requests fast enough (regardless of transfer speed) and they have formed a backlog that must be cleared before additional processing can occur. This can very easily occur with image sequences (loads of little files) versus movies (single big files).

Also, because Premiere Pro is 64-bit and the QuickTime libraries are 32-bit, Premiere cannot use QuickTime directly. To work around this, Adobe passes information from 64-bit Premiere to its 32-bit Quicktime helper process via the computer’s network stack. This may introduce another bottleneck, which I’d think you’d be able to see in the Network tab. Renders to non-QT formats may be faster.

Walter Soyka
Principal & Designer at Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog – What I’m thinking when my workstation’s thinking
Creative Cow Forum Host: Live & Stage Events

[Jim Hoyle]

The queue length is between 0.00 and 0.05. To me, that doesn’t seem like the problem.

The export is extremely slow. I would estimate about 70% slower than my 5 year old system (where the biggest differences were motherboard and processor).

[Hidalgo Rabelais]

Hi, just found this post having ecountered the same problem.

To me the bug seemed to be something with the footage and sequence settings.
It was a 4:3 project with a weirdo footage with something like 700×576, I was going to reframe it onto a 720 sequence.

After importing, as soon as I dragged the footage CS6 prompted me to choose between keeping the sequence setting or changing them in order to match the footage’ ones.
If I kept my sequence settings the rendering time became insanely long, almost crazy and definitely unworkable with.

If I changed the sequence settings to match the footage’s everything worked out smootly and without problems.
I know it seems crazy but that’s what worked for me, hope it helps.

P.S.I am working with an outdated win7 notebook with a core2duo 2,53 Ghz and 4GB ram and all the footage onto a lacie1Tb with esata..so problems with rendering were expected but this seemed to be the matter with my setup.

[Photos Cubano]

Hi may name is ray I was have the premier pro 2015 and it was very slow .
I follow you tips and it work .
but I don’t Know how much so I don’t burn may machine .
My Email is Cubanophoto@gmail.com
208 573 4928 cell .