Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe After Effects Upgraded to Quadro K5000 Mac, and almost no speed improvement in AE CS6 or AE CC 2014?

  • Upgraded to Quadro K5000 Mac, and almost no speed improvement in AE CS6 or AE CC 2014?

    Posted by Larry Wheeler on July 10, 2014 at 3:07 pm

    Been running AE CS6 for a long while now on my Mac Pro with a Quadro 4000 Mac Video Card. Performance was always pretty slow in 1080i, even in basic work. I have a Mid 2012 Mac Pro with 12 core @ 3.06 Processors running on 10.9.4. This one has 64GB RAM, and is SSD based on the OS, with a dedicated SSD just for AE cache files as well.

    I upgraded to AE CC 2014, and installed the new K5000 Video card. Speeds have improved, very slightly, if at all. Is there something I am missing here? I use AE for a lot of my graphics, and the stuff I am doing isn’t heavy lifting. It’s 1080i ProRes- 30 to 40 second comps with pre-rendered backgrounds (that never change) and basic 2d text that doesn’t even move. That’s it, yet with one line of text on a pre-rendered background, it takes 3.5 to 5 minutes to render in ProRes for a 44 second clip. That is in CS6, and CC 2014. Times were identical on the older configuration with the Quadro 4000.

    Changing to “render multiple frames simultaneously” doesn’t help in either scenario. This machine is easily trounced in performance by my Retina MacBook Pro on AE CC, and by the HP “Mobile Workstation” PC Laptop top with AE CC. Both of these (admittedly decked out) laptops turn out the same material in far less time.

    What am I missing here? Any help would be appreciated!

    Ericbowen replied 11 years, 9 months ago 6 Members · 18 Replies
  • 18 Replies
  • Michael Szalapski

    July 10, 2014 at 3:12 pm

    [Larry Wheeler] ” Times were identical on the older configuration with the Quadro 4000…

    What am I missing here?”

    You are missing the fact that the GPU will not have any effect at all on what you are doing.
    See this [link] about the GPU in AE.

    It does sound like it’s taking too long though. What are your memory and multiprocessing settings? Cache settings? Etc. (Screenshots would help.)

    – The Great Szalam
    (The ‘Great’ stands for ‘Not So Great, in fact, Extremely Humble’)

    No trees were harmed in the creation of this message, but several thousand electrons were mildly inconvenienced.

  • Larry Wheeler

    July 10, 2014 at 3:21 pm

    Thanks for the link Michael. I somehow never knew the GPU wasn’t part of the equation with AE. My apologies.

  • Michael Szalapski

    July 10, 2014 at 3:44 pm

    Turn on Render Multiple Frames Simultaneously and set CPUs to use for other applications to something other than 0. Try a render in the Render Queue and see if that makes a difference.

    Then try these tips and resources [link]. (Especially this one [link] and this one [link]).

    – The Great Szalam
    (The ‘Great’ stands for ‘Not So Great, in fact, Extremely Humble’)

    No trees were harmed in the creation of this message, but several thousand electrons were mildly inconvenienced.

  • Ericbowen

    July 10, 2014 at 3:53 pm

    Setting CPU’s to use on other applications to something other than 0 wont speed AE render queue time up. However set multi processing on and the ram per thread to 2 to 4GB and see how that works. The comp decides how much ram you need per thread but those are the normal settings for standard comps. Also a screen pic of OSX CPU threading meter would help identify what your seeing.

    Eric-ADK
    Tech Manager
    support@adkvideoediting.com

  • Ian Mapleson

    July 10, 2014 at 3:58 pm

    Larry Wheeler writes:
    > … I somehow never knew the GPU wasn’t part of the equation with AE. My apologies.

    Actually it very much does matter if you’re using the RayTrace3D function, which
    employs CUDA acceleration. Massively faster than the main CPU(s). My system has
    four GTX 580 3GB cards for this (faster than two Titan Blacks, but much cheaper).
    Other parts of AE can exploit OpenGL or CUDA to run faster aswell; details on the
    Adobe site here:

    https://blogs.adobe.com/aftereffects/2012/05/gpu-cuda-opengl-features-in-after-effects-cs6.html
    https://helpx.adobe.com/after-effects/using/rendering-opengl.html

    And indeed on this site, see:

    https://forums.creativecow.net/thread/2/1019120

    I’ve tested a K5000 with Viewperf, it’s quite a lot faster than a 4000, at least
    where the GPU is indeed the bottleneck. See:

    https://www.sgidepot.co.uk/misc/viewperf.txt

    Ian.

    SGI Guru

  • Michael Szalapski

    July 10, 2014 at 4:04 pm

    [EricBowen] “Setting CPU’s to use on other applications to something other than 0 wont speed AE render queue time up.”

    But it will help keep things running smoothly. The OS and any programs running in the background need something to run on or it can cause issues.

    [Ian Mapleson] “Actually it very much does matter if you’re using the RayTrace3D function, which
    employs CUDA acceleration.”

    Ian is right. As the link I shared says, if you ever use ray-traced rendering, a GPU makes a huge difference. (However, the ray-traced 3d rendering feature is considered obsolete now that we have C4D included with AE.)

    – The Great Szalam
    (The ‘Great’ stands for ‘Not So Great, in fact, Extremely Humble’)

    No trees were harmed in the creation of this message, but several thousand electrons were mildly inconvenienced.

  • Ian Mapleson

    July 10, 2014 at 4:13 pm

    Michael Szalapski writes:
    > … (However, the ray-traced 3d rendering feature is considered obsolete now that
    > we have C4D included with AE.)

    I must confess my knowledge of C4D is minimal. Can it be GPU accelerated? I was wondering
    how it would compare for rendering something like this (reflections gone whacko):

    https://www.sgidepot.co.uk/misc/cuda.101_Frame96.jpg

    That takes about 15 mins to render on four GTX 580s (Titan Black = approx. 25 mins)

    Ian.

    SGI Guru

  • Ericbowen

    July 10, 2014 at 4:33 pm

    The editor is not running into issues with AE not completing the render or crashing. The issue is the amount of time compared to dual or quad core laptop. The OS moderates these interrupts and should not have any issues interrupting the cpu’s when needed for the OS or another app. By default this set to 0 likely on the laptops as well. Setting a CPU to idle for non use by the application just is slowing it down in this case not speeding it up. If an editor is running into issues with AE crashing then that is a setting to look at. If not then it wont change the results here.

    Eric-ADK
    Tech Manager
    support@adkvideoediting.com

  • Walter Soyka

    July 10, 2014 at 5:04 pm

    [EricBowen] “By default this set to 0 likely on the laptops as well. Setting a CPU to idle for non use by the application just is slowing it down in this case not speeding it up. If an editor is running into issues with AE crashing then that is a setting to look at. If not then it wont change the results here.”

    That’s not my experience at all, but this is highly situationally dependent.

    https://blogs.adobe.com/aftereffects/2010/03/performance-tip-dont-oversched.html

    Walter Soyka
    Designer & Mad Scientist at Keen Live [link]
    Motion Graphics, Widescreen Events, Presentation Design, and Consulting
    @keenlive   |   RenderBreak [blog]   |   Profile [LinkedIn]

  • Ericbowen

    July 10, 2014 at 5:18 pm

    Remember the OS is handling the threading and scheduling for all applications such as editors like Premiere or FCPX without any cpu setting control. This is something the OS is designed to do regardless of whether an application has an option for that or not. The differences occur in the priority assigned to the applications and the interrupts for each application call. For example an input command from an application can have a much higher priority than a data execute command and so on and so forth. If the editor is continuing to work on other applications and the input latency starts becoming an issue due to the scheduling and time it takes to interrupt cores then leaving a core idle will often alleviate that. However if that application has a high enough priority and the background application has the correct status for executing data this is negotiated efficiently by the OS.

    Eric-ADK
    Tech Manager
    support@adkvideoediting.com

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy