Activity › Forums › DaVinci Resolve › Expected rendering performance.
-
Expected rendering performance.
Posted by Dmitry Kitsov on February 4, 2012 at 11:02 amI am Beta “testing” the 8.2 v3 Resolve on Windows. I am curious what rendering performance to expect. I am referring to a final output and not a preview render, of course.
What performance you guys and girls get? Let’s have a hypothetical ProRes .mov with one node of primary color correction applied rendering as a ProRes. Assuming that both hard drives (source and render) are not a bottleneck factor what rendering speed in terms of fps should one expect in a system with 1 GPU (plus gui), system with 2 GPUs (plus gui)?
Thanks a lot in advance.Luigi Valtulini replied 14 years, 3 months ago 10 Members · 22 Replies -
22 Replies
-
Lauri Laidna
February 4, 2012 at 11:58 amI’m getting around 35-50fps (DNxHD 1080p source and output) with different complexity grades on them. It’s basically up to 2x real time all the way. R3D Half Resolution Good quality debayer with grades on them I get above realtime without RedRocket. R3D debayering is done solely by the CPU if you don’t have RedRocket.
With only one GTX285 graphics card running both GPU+GUI I had some issues. The performance did go down after some work. I think the 1GB of memory ran out. After restartting Resolve it was up to speed again until it got slower again after some time. GPU memory usage was maxed out. So always go with 2 graphics card!
So I get enough performace out already. Next step for me would be to upgrade to GTX580. I don’t think you’d need multi-GPU solution when working with 1080p.
Windows Professional, GTX285 as GPU, GTX280 as GUI, 3930K @ 4.4GHz, 32GB RAM
-
Margus Voll
February 4, 2012 at 4:36 pmdepends if you need realtime NR and how many nodes with it.
NR and multiple blur nodes if needed will bring your system down with
only 2 cards. This is expander and 3 beefy cards are good.It is like with cars, you can go 90 with most of them but 150 with only good setup.
Depends on your needs.
—
Margus
-
Dmitry Kitsov
February 4, 2012 at 5:38 pmThanks, Lauri
By 1 GPU (plus gui) I of course meant 1GPU for acceleration plus 1 for gui (two altogether), and by 2 GPUs (plus gui) I meant three altogether. Could you try running a ProRes render for me (more critical to me as I work mostly with FCP people rather than Avid people)? -
Dmitry Kitsov
February 4, 2012 at 5:43 pmThanks, Margus. I am aware of the NR performance hit. I am however not looking for a general philosophical info and race track metaphors. I really am looking to compare the real world performance (for a very specific reason) with relatively simple conditions (ie. 1080p ProRes in – 1080p ProRes Out, one nod, primary color correction only)
-
Margus Voll
February 4, 2012 at 7:51 pmAs you know prorez depends mostly on your cpu compared to uncompressed
so you have to keep that in mind.—
Margus
-
Dmitry Kitsov
February 5, 2012 at 2:56 amReally? So GPU acceleration id only used for grading process and not the render itself?
-
Jake Blackstone
February 5, 2012 at 4:41 amWait, what? Did I miss an announcement? Does Resolve on Windows now writes Prores?
-
Timo Teravainen
February 5, 2012 at 6:45 amPeople say it does..!? Haven’t been able to test it yet, but if that’s true, it’s huge!
-
John Michaels
February 5, 2012 at 6:55 amI can confirm it does. And it is glorious. 😉
I get around 50fps render out to ProRes with my GTX 560Ti
-
Dmitry Kitsov
February 5, 2012 at 7:17 amMichael, do you really mean 50fps render as in final output render? If so what are your system specs?
I am on GTX285 (GUI), plus 2x GTX580s (image processing, Xeon 5690, 24GB. Both hard drives are raid systems with sustained 350MBps. All I get is 15fps ProRes render.
Reply to this Discussion! Login or Sign Up