-
Longer Render Times depending on Target drive causing GPU to not be utilized
I was just rendering/encoding with the MainConcept AVC using the Internet HD 1080p template customized to use CUDA GPU. My source files are on drive N (int SATA 2 drive) and SVP 12 runs from drive C (another SATA 2 drive). To speed things up I thought I would render to drive G an external USB drive.
I also run an EVGA Nvidia GTX 570 card and utility that shows the GPU utilization in the systray area.
What I noticed is that the GPU is utilized in the beginning, but then it drops to 0% and task manager shows all 12 CPUs near 100%. The render will finish in about 28min for my 13 minute video.
If I change my target to drive C, the GPU utilization bounces around 30-70% and the render completes in about 12min.
Normally it is not a good performance choice to render to the OS drive, which is why I am sharing this experience. Just because you can choose the option of using the GPU and it can find one too, does not mean it is used during the whole process.
-
4 Replies
-
Hey Mark,
What happens when you render back to the same (N) drive?
Jeff
2-Xeon X5680 @ 3.33, EVGA SR-2 Mobo, 48GB DDR3, GTX 580 3072MB, 16TB Attached Storage, Win7, Vegas 11 x64
-
[Mark Barton] ” To speed things up I thought I would render to drive G an external USB drive.”
“Speedy” is not a word that I wouldn’t use to describe an external USB drive (unless maybe it was USB 3). From your tests you have proven that it became the bottleneck. What people don’t realize about USB is that it uses the CPU for everything it needs to do unlike Firewire which is an intelligent interface. So Vegas was using the CPU while the USB drive was contending for the CPU which is why the CPU maxed out and the GPU was just waiting around for more work to do.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
10:04 min when I render to the same drive N as the source.
-
[Mark Barton] “10:04 min when I render to the same drive N as the source.”
So rendering back to the same drive is actually the fastest. This is how I always work with everything on one project eSATA drive.
~jr
http://www.johnrofrano.com
http://www.vasst.com
Reply to this Discussion! Login or Sign Up