Benchmarking results continued

JN- wrote on 1/18/2020, 12:56 PM

Continued from the now locked “Benchmarking” thread ...

Please use the user data input format below when posting your benchmarking information.

Best to mostly just post results here, thanks.

The "date" entry that I add into the "Comments" column is for when the user first submits results, it isn't updated for any later user updates. It's of use in locating a users post in this thread or the original Benchmarking thread.

You can download the benchmarking project at this link here ...

When you’ve run the benchmarking project and have your render and average FPS values, post them here in this thread. You can use the “Sample User Data” items that are supplied in the ZIP file if necessary. I’ll then update the screenshot results here and I’ll also update the spreadsheets and screenshots in the ZIP file. Note that the render time results are for the full project duration, the average FPS value is for the “Region 1” duration only. Please enter only the same "Average FPS" value for all of your different encoder and frame size entries.

Don't change the Project properties. Whether checking your FPS/rendering UHD or FHD, leave as is.

Templates and user data input with examples … Use similar for Nvenc, QSV, VCE, and CPU encoders.

The data rates of the 2 templates below is 24/12 for FHD and 50/28 for UHD. So irrespective of what encoder you're using, just use those data rates.

My rendered out file sizes on disc. You should get somewhat similar, but not necessarily the exact same results.

FHD size = 48.9 mb ..... Data rate = 9,583 kbps

UHD size = 114 mb ..... Data rate = 22,611 kbps

If your output file sizes and data rates are not similar, then check that you are using the correct render template settings.

Sample User Data Input and example, text file versions are in the ZIP file …

Use the instructions in the screenshots below to get the Average FPS value …

If possible set the Dynamic ram Preview to zero while doing so.

Note that the region 1 section above is only used to get the average FPS value, do render out the full length project to get the various render times.

Results ...

Screenshots below from spreadsheet of all users up to date data ...

Sorted on "Render" times and sorted on Average "FPS"...

The older "Benchmarking" thread.

Back to post

Comments

JN- wrote on 2/4/2021, 4:40 AM

@set Aok, will add date to comments, good idea, will update all later and post here when done.

JN- wrote on 2/4/2021, 10:01 AM

https://www.vegascreativesoftware.info/us/users/profile/set/

Is updated now.

diverG wrote on 2/4/2021, 10:41 AM

Have been meaming to play with benchmarking for some time. Wet day in lockdown provides ideal opportunity.

   User name       :DiverG
   Machine           :OB Sys 1 in signature
   VP version       :18
   VP Build number       :434
   CPU           :i7-8086K
   Cores           :6
   GPU           :GTX 1060 6Gb
   iGPU           :UHD 630
   OC           :4.3GHz Air cooled

   Render frame size   :FHD
   HW Acc.           :Nvidia
   Render As       :Magix Avc
   Encode mode       :Nvenc
   Render time       :01:10s
   FPS           :14.88 (render rate)

Region 1 : FPS 5.2 avg Corrected ( time line viewing)

Comments       :Prefs Video Set 0 Otherwise low memory error whilst rendering
*********************************************************************************************************************************   Render frame size   :UHD
   HW Acc.           :Nvidia
   Render As       :Magix HEVC
   Encode mod   :Nvenc
   Render time       :02:07s
   FPS           :8.21s (render rate)

Region 1 : FPS 5.2 avg Corrected ( time line viewing)

Comments :Prefs Video Set 0 Otherwise low memory error whilst rendering

Thanks for standardising this task

Edit (5th Feb) Region 1 now corrected

JN- wrote on 2/4/2021, 12:10 PM

@diverG Thanks for your input, I appreciate you going to the trouble. A few small points to clear up ...

An issue that appears quite a lot, maybe I need to update the user data input. The Avg. FPS value for the same machine, has to be the same, similar value, irrespective of what it was rendered out at, UHD or FHD. The project properties are fixed, so the Avg. playback for region 1 is always the same. In your case its either 8.21 or 14.88 but not both.

Im not sure what your entry for Region 1 is, its not necessary, or part of required input. Thank you.

diverG wrote on 2/4/2021, 12:48 PM

Senior moment. The figures relate to the rendering of region 1, not the time line playback. Will correct tomorrow as that pc is currently tied up. Pls accept applogies.

Edit: Now corrected.

JN- wrote on 2/4/2021, 12:59 PM

@diverG No need to apologise, looking forward to your updated results.

JN- wrote on 2/4/2021, 6:53 PM

I added in the date in the comments column. This is merely the time when a user started to enter data, it doesn't account for any later updates. Can be useful to quickly find in either of the two Benchmarking threads where the data was entered. Will appear with the next users data entry update.

JN- wrote on 2/6/2021, 6:56 PM

@diverG Only saw your updated comment a while ago. Is updated now.

MP- wrote on 2/14/2021, 1:59 PM

@JN

New slightly improved times with new motherboard - PSU.

User name       :MP-
   Machine           :OB
   VP version       :18
   VP Build number       :434
   CPU           :i9-10980XE
   Cores           :18
   GPU           :AMD RX-6800XT
   iGPU           :none
   OC           :No
   Render frame size   :UHD
   HW Acc.           :AMD
   Render As       :Magix AVC
   Encode mode       :VCE
   Render time       :00:58s
   FPS           : 18.5 fps
   Comments       : MSI X299 Creator, source, scratch and rendering delivery disks are 3 Samsung 970 Plus, OS Disk is Samsung Evo 840 SSD

User name       :MP-
   Machine           :OB
   VP version       :18
   VP Build number       :434
   CPU           :i9-10980XE
   Cores           :18
   GPU           :AMD RX-6800XT
   iGPU           :none
   OC           :No
   Render frame size   :UHD
   HW Acc.           :AMD
   Render As       :Magix AVC
   Encode mode       :CPU
   Render time       :01:32s
   FPS           : 18.5 fps
   Comments       : MSI X299 Creator, source, scratch and rendering delivery disks are 3 Samsung 970 Plus, OS Disk is Samsung Evo 840 SSD

User name       :MP-
   Machine           :OB
   VP version       :18
   VP Build number       :434
   CPU           :i9-10980XE
   Cores           :18
   GPU           :AMD RX-6800XT
   iGPU           :none
   OC           :No
   Render frame size   :FHD
   HW Acc.           :AMD
   Render As       :Magix AVC
   Encode mode       :VCE
   Render time       :00:29s
   FPS           : 18.5 fps
   Comments       : MSI X299 Creator, source, scratch and rendering delivery disks are 3 Samsung 970 Plus, OS Disk is Samsung Evo 840 SSD

User name       :MP-
   Machine           :OB
   VP version       :18
   VP Build number       :434
   CPU           :i9-10980XE
   Cores           :18
   GPU           :AMD RX-6800XT
   iGPU           :none
   OC           :No
   Render frame size   :FHD
   HW Acc.           :AMD
   Render As       :Magix AVC
   Encode mode       :CPU
   Render time       :00:34s
   FPS           : 18.5 fps
   Comments       : MSI X299 Creator, source, scratch and rendering delivery disks are 3 Samsung 970 Plus, OS Disk is Samsung Evo 840 SSD

JN- wrote on 2/14/2021, 2:19 PM

@MP- Will update later. Actually, I may wait a little while and do your's and @Grazie's Monsta2 together. I suspect he should be ready to let it loose on the forum anytime now? If not I will just update yours.

@MP- In the meantime, I have updated the SS's and added them to the ZIP.

Grazie wrote on 2/14/2021, 2:29 PM

@JN- I suspect he should be ready to let it loose on the forum anytime now? If not I will just update yours.

@JN- Not soon. I suggest you post. 😉

JN- wrote on 2/14/2021, 2:40 PM

@Grazie 👍

JN- wrote on 2/14/2021, 3:00 PM

@MP- Is updated now.

Grazie wrote on 2/19/2021, 6:25 AM

@JN- Arrghhh - I'm drowning in Links, Dropsy Boxes, SSs and Vegies and Media : Is there not just ONE link that gives me what I'm wanting? Please keep it simple for me: A "One Stop Shop" . . .

Dexcon wrote on 2/19/2021, 6:36 AM

@Grazie ... I've got the Red Car Test (2.9 GB) on an external HDD from years ago and am currently copying it to OneDrive though the copy/paste process is very slow. I'll PM you tomorrow (AU time) with a OneDrive link so that you can DL it though I'll have to work out the link process again because I do that so rarely. Cheers.

RogerS wrote on 2/19/2021, 6:36 AM

While the process is confusing at first, the download link is on the first page and includes instructions and the veg and media for download.

JN- wrote on 2/19/2021, 6:46 AM

@Grazie Everything you need is via the link on my very 1st. post in this thread. I don't think it needs to be said, but just in case anyway. ... don't modify the project properties, leave as is whether you are testing render output times or Average FPS. Always only supply one single value of Avg. FPS for all of your entries, thank you.

TheRhino wrote on 2/19/2021, 8:11 AM

@JN- Here are my results from when I was testing-out the Nvidia 3060 Ti. I returned it because it had about the same performance as my VEGA 64 LQ for my typical 4K workflow but blocked the adjacent PCIe with its fans...

Sample Project 4K to UHD
User name: TheRhino
   Machine: OB
   VP version: 18
   VP Build number: 373
   CPU: 9900K
   Cores: 8
   GPU: Nvidia RTX 3060Ti
   iGPU: Intel 630
   OC: YES – 4.9 ghz
   Render frame size: UHD
   HW Acc.: NVENC
   Render As: Magix AVC
   Encode mode: NVENC
   Render time: 01:20
   FPS: 12.5 fps
   Comments: Nvidia Studio driver 460.89. Source & target on separate M.2 RAIDs.

Sample Project 4K to FHD
User name: TheRhino
   Machine: OB
   VP version: 18
   VP Build number: 373
   CPU: 9900K
   Cores: 8
   GPU: Nvidia RTX 3060Ti
   iGPU: Intel 630
   OC: YES – 4.9 ghz
   Render frame size: FHD
   HW Acc.: NVENC
   Render As: Magix AVC
   Encode mode: NVENC
   Render time: 0:47
   FPS: 12.5 fps
   Comments: Nvidia Studio driver 460.89. Source & target on separate M.2 RAIDs.

Sample Vegas11 RedCarTest
User name: TheRhino
   Machine: OB
   VP version: 18
   VP Build number: 373
   CPU: 9900K
   Cores: 8
   GPU: Nvidia RTX 3060Ti
   iGPU: Intel 630
   OC: YES – 4.9 ghz
   Render frame size: FHD
   HW Acc.: NVENC
   Render As: Magix AVC
   Encode mode: NVENC
   Render time: 0:19

   Comments: Nvidia Studio driver 460.89. Source & target on separate M.2 RAIDs

JN- wrote on 2/19/2021, 8:28 AM

@TheRhino Thank you, very useful having this GPU result, will probably be a popular choice going forward. If its ok with you, I’ll wait for the Monsta2 results, and post all together, Grazies should be in anytime soon😂.

TheRhino wrote on 2/19/2021, 11:10 AM

@JN- Ya I just wanted to get my info posted in time so you could add it with Grazie's update... It helps all to see where the new 3xxx GPUs land. Personally I recommend the 3060 Ti as the new low-end ($400 USD) best bang/buck GPU. For about the same price, it outperforms the AMD 5700 XT in other apps & some 3rd party plugins, etc...

I was considering getting the faster 3080 for a 2nd workstation upgrade but that project got postponed when I had to upgrade my MAC hardware for a big incoming FCP job that requires collaboration... I know the Vegas team got approval from Apple to provide ProRes RAW support (and will also add BRAW...) but I couldn't wait. Plus, no one knows how fast RAW will work with Vegas, especially if it doesn't take full advantage of these new CPUs & GPUs... It may really mean waiting until the next full version release (V.19) or beyond... to see it all come together & in the meantime I'm getting paid NOW for RAW input / export... But no, I didn't run-out and buy a $7,000+ 2019 Mac Pro... IMO what has always made Vegas great is its ability to run on affordable hardware without making proxies, etc. And I like that I can just copy the source files & VEG and edit on another workstation...

JN- wrote on 2/19/2021, 11:46 AM

@TheRhino "It may really mean waiting until the next full version release (V.19) or beyond." Probably.

Your results are updated in the SS's at ZIP location only. Will fully update with Grazies.

@TheRhino Your results are fully updated now, thank you.

Grazie wrote on 2/23/2021, 12:55 AM

@JN- - Wow, I had made a Pig's Ear out of it! But with some excelllent Guidance from @RogerS ( a TOTAL Gent ), got me through the Night - literally! - He also suggested I do a Mainconcept Encode. Does this assist others?

@JN- I've read through others posts here and I see some inconsistencies that I do not understand - not unusual for me.

++++++++++++++++++++++++++++++++++++++++

User name: Grazie
    Machine: MONSTA2!
    VP version: 18
    VP Build number: 434
    CPU: i9-10900X CPU @ 3.70GHz
    Cores: 10
    GPU: EVGA RTX 3080 XC3 Ultra 10GB
    iGPU: NONE
    OC: No
    Render frame size:UHD
    HW Acc.: Nvidia
    Render As:Magix AVC
    Encode mode:NVENC
    Render time: 1:15
    FPS:11
    Comments:

++++++++++++++++++++++++++++++++++++++++

User name: Grazie
    Machine: MONSTA2!
    VP version: 18
    VP Build number: 434
    CPU: i9-10900X CPU @ 3.70GHz
    Cores: 10
    GPU: EVGA RTX 3080 XC3 Ultra 10GB
    iGPU: NONE
    OC: No
    Render frame size:UHD
    HW Acc.: Nvidia
    Render As:Magix AVC
    Encode mode:Mainconcept
    Render time: 00:52
    FPS:11
    Comments:

++++++++++++++++++++++++++++++++++++++++

User name: Grazie
    Machine: MONSTA2!
    VP version: 18
    VP Build number: 434
    CPU: i9-10900X CPU @ 3.70GHz
    Cores: 10
    GPU: EVGA RTX 3080 XC3 Ultra 10GB
    iGPU: NONE
    OC: No
    Render frame size:FHD
    HW Acc.: Nvidia
    Render As:Magix AVC
    Encode mode:NVENC
    Render time: 00:46
    FPS:11
    Comments:

++++++++++++++++++++++++++++++++++++++++

User name: Grazie
    Machine: MONSTA2!
    VP version: 18
    VP Build number: 434
    CPU: i9-10900X CPU @ 3.70GHz
    Cores: 10
    GPU: EVGA RTX 3080 XC3 Ultra 10GB
    iGPU: NONE
    OC: No
    Render frame size:FHD
    HW Acc.: Nvidia
    Render As:Magix AVC
    Encode mode:Mainconcept
    Render time: 00:52
    FPS:11
    Comments:

JN- wrote on 2/23/2021, 2:26 AM

@Grazie

#1 Valid encode modes can be CPU, Nvenc, Vce , Qsv or Cuda. Please modify your data accordingly.

#2 Please confirm the duration of your FHD & UHD renders.

Grazie wrote on 2/23/2021, 2:56 AM

@JN- Well, MainConcept = CPU. I’ll reconfirm all four, again, I’m not expecting a difference. Why are you asking? Are they too high or low?