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.

Comments

rtbond wrote on 1/26/2020, 6:30 AM

I see four spreadsheets in the benchmarking zip I downloaded. Which of this to I populate with my results? What do I do with the results (place back in the Dropbox?)

JN- wrote on 1/26/2020, 6:43 AM

Hi @rtbond Rob, no need to modify the spreadsheet, I do that and then I update the spreadsheet screenshots in my first post here, in this thread. I then place the newly updated ss back into the zip with the newly updated screenshots.

All you need to do is post your results here, in this thread. You can use the user input examples in the zip to get a starting idea of whats needed. See other users posts in the older Benchmarking thread.

rtbond wrote on 1/26/2020, 7:45 AM

OK, thanks. Trying an AVC/MP4 render Vegas is producing a memory low error, although Windows indicates over 53 GB of memory is free. Vegas Pro 17 then went "Not Responding". There is 8 GB of RAM on the EVGA GeForce RTX 2070 SUPER XC ULTRA card.

JN- wrote on 1/26/2020, 8:07 AM

@rtbond
Hi Rob, if you have VP16, or trial version of, maybe use it instead of VP17.

Also see threads ...

https://www.vegascreativesoftware.info/us/forum/low-memory-error-could-not-finish-rendering--115934)

https://www.vegascreativesoftware.info/us/forum/the-system-is-low-on-memory-4k-render-error-when-it-clearly-is-not--116565/

https://www.vegascreativesoftware.info/us/forum/v17-hangs-crashes-and-slow-on-browsing-through-project--116626/#ca725799

Sniping117 wrote on 1/26/2020, 10:04 AM

I really feel like something is wrong with my PC. I get less than 1 FPS average and the 1080p render took me a bit over 4 minutes. I tried uninstalled my drivers with DDU and re-installing VP17 but it just keeps messing with my rendering. Had a 10 min video yesterday which took 2 hours and 17 min to render. My CPU never goes above 30% load and GPU stays around 1%-2% load. Might try going back to VP16.

Edit: Tried it on VP16 and got 7-10 FPS on avg and render time took 00:56. I guess my PC just doesn't like VP17

Username: Sniping117

Machine: OB

VP version: 17

VP Build number: 387

CPU: i9-9900k

Cores: 8

GPU: RTX-2080

iGPU: UHD 630

OC: Yes

Render frame size: FHD

HW Acc.: None

Encode mode: Nvenc

Render As: Magix Avc

Render time: 04:07

FPS: 0.7-1

rtbond wrote on 1/26/2020, 10:06 AM

I set Dynamic RAM Preview to ZERO (per https://www.vegascreativesoftware.info/us/forum/low-memory-error-could-not-finish-rendering--115934) under the Vegas "Preferences, Video tab) and that stop the low memory errors. The original value of the Dynamic RAM Preview was 200 MB, the Vegas default. I am puzzled as to why the Dynamic RAM Preview is having this effect, but it appears to.(I see this has been logged as an "unofficial known issue")

Here are the benchmark results. For HEVC render, the time was slighlty higher (1:47)

User name       :rtbond
   Machine           :OB
   VP version       :17
   VP Build number       :387
   CPU           :i9-10940X
   Cores           :14
   GPU           :NVIDIA GeForce RTX 2070 Super
   iGPU           :None
   OC           :No
   Render frame size   :UHD
   HW Acc.           :Nvidia
   Encode mode       :Nvenc
   Render As       :Magix Avc
   Render time       :1:39
   FPS           :5.6 to 10 fps (region 1), VP17 often stops responding after looping playback of this region
   Comments       : Set the Dynamic RAM Preview to ZERO (Preferences) to stop the "Low on Memory" error in VP17, CPU utilization remained low (i.e., below 20%), which I suppose this expected for a GPU-based render.

For fun, I changed the Encode Mode for AVC render to "Mainconcept AVC" (which I assume is a CPU render) and the render time increased to 1:59 and the CPU utilization ran from 50 -100 %, with the CPU clock rate jumping to 4.1 GHz from the 3.3 GHz base clock.

JN- wrote on 1/26/2020, 10:22 AM

@Sniping117 I see you're not using any HW Acc., so maybe those times are ok?

If you get a set of results from VP16 that's better I'll update the SS accordingly.

@rtbond Glad you got around the issue Rob.

I'll add both sets of data shortly and post when done, thanks.

Sniping117 wrote on 1/26/2020, 10:31 AM

@JN- whenever I enable HW Acc. in VP17, my preview gets all messed up having black flashes etc and the renders get all screwed up as well, resulting in loops, footage completely being left out so I'm forced to turn that off in VP17. In VP16 it works perfectly fine with HW Acc. turned on.

Username: Sniping117

Machine: OB

VP version: 16

VP Build number: 424

CPU: i9-9900k

Cores: 8

GPU: RTX-2080

iGPU: UHD 630

OC: Yes

Render frame size: FHD

HW Acc.: Nvidia

Encode mode: Nvenc

Render As: Magix Avc

Render time: 00:56

FPS: 7-10

JN- wrote on 1/26/2020, 10:44 AM

@Sniping117 So what I'll do for now is just enter your VP16 data until/if the VP17 issues get resolved, if that's ok with you? VP17 as I have found has memory handling issues. Try several of these, if you haven't already ...

Set Dynamic Ram Preview to zero; Get latest Studio driver; change/experiment with settings in the I/O tab; Reduce the number of "threads"

JN- wrote on 1/26/2020, 11:13 AM

@rtbond and @Sniping117 I've updated your test results to my first post in this thread and also the downloadable ZIP file is also updated. Please do let me know if there are any errors in my updates and feel free to add any more entries here if you desire. Thank you.

rtbond wrote on 1/26/2020, 11:40 AM

@JN- : I get slightly better FPS performance when I use my secondary display (4k, HDR10), which matches the project settings. The FPS in region 1 ranges from 6.8 to 12 fps.

I also rendered Magix AVC at FHD (25 fps) in 1:01.

JN- wrote on 1/26/2020, 11:55 AM

Excellent @rtbond I'll update accordingly later, not at PC at the moment.

JN- wrote on 1/26/2020, 2:14 PM

@rtbond

Hi Rob, is updated now.

JN- wrote on 1/26/2020, 2:51 PM

@Sniping117 @rtbond FWIW my render times in VP17 are slower than VP16.

Sassylola wrote on 1/27/2020, 3:57 PM

User Name : lolasassy ( my 2 dogs name )

Machine : OB

VP version : 17

Build Number : 387

CPU : Ryzen 3900X

Cores : 12

Ram: : 32gb 3600mhz DDR4

GPU : MSI RTX 2070 Super (Studio Drivers latest)

Power Supply : Corsair 850X

OC : Partial

Render frame size : FHD and UHD

HW Acc : Nvidia

Encode mode: : Nvenc

Render as : Magix Avc

Render time : See Below

FPS : See below

My UHD results:

I had to set Dynamic Ram preview to 0. Was getting low memory message.

No OC:

Render time: 1:31.

Region 1 - 7 to 13 fps.

With Ryzen Master OC set to creator mode and precision boost overdrive

Render time was 1:29 seconds.

No region 1 taken.

With Ryzen Master and MSI afterburner ON. Ran afterburner and used their recommended OC settings for VC. I did change memory clock +500mhz.

Render time: 1:30.

Region 1 - 8 to 14 fps.

WITHOUT Ryzen Master on and Afterburner ON.

Render time: 1:30.

Region 1 - 7 to 14 fps.

My FHD results:

With no OC:

Render took 54 seconds.

With afterburner running and NO Ryzen Master,

render took 55 seconds.

Region 1: Crash then after restart 8 to 14 fps.

With Ryzen Master ON and Afterburner ON:

Render: 55 seconds

Region 1 7 to 14 fps.

While testing region 1 after a few passes frame counter would stop and Vegas would not respond. This was with dynamic ram set to 0 and 200. The playhead would still move but the preview window would be stuck at a certain frame ( frame 360 for me). This also happens with Afterburner and Ryzen Master set to OFF.

Now I am wondering if it is my VC?

So system was a second slower with OC. Now these are mild OC. I don't have the nerve to push it further. I spent to much money and time putting this thing together.

JN- wrote on 1/27/2020, 4:10 PM

@Sassylola Great stuff, not at PC now, I'll update later this evening.

JN- wrote on 1/27/2020, 5:45 PM

@Sassylola Hi Lolasassy, I've updated your results now. If you have any changes to make, additions etc let me know. I averaged the 3 different FPS values to arrive at the 10.5.

Sassylola wrote on 1/27/2020, 6:15 PM

J-N, I will update my results when I receive my Radeon Vll. Supposed to arrive Wed from Amazon. I took back the 2070 Super. The first Radeon I had was defective. Will see if 2nd one works.

Right now using my old R9 380. Tried running your benchmark was getting .3 fps. Frame Counter was trying to keep up. I stopped the test after about 10 seconds.

JN- wrote on 1/27/2020, 6:26 PM

@Sassylola Excellent. Looking forward to the Radeon playback times especially!

james-ollick wrote on 1/27/2020, 6:46 PM

Username: james-ollick

Machine: OB

VP version: 17

VP Build number: 387

CPU: i9-9900k

Cores: 8

GPU: RX580

iGPU: UHD 630

OC: No

Render frame size: UHD

HW Acc.: AMD

Encode mode: Intel QSV

Render As: Magix HEVC/AAC MP4 - Internet UHD 2160p 25 fps (Intel QSV)

Render time: 1:04 (only between the markers)

Render time: 1:36 (Full Project)

FPS: 9 average

==============================================================

Username: james-ollick

Machine: OB

VP version: 17

VP Build number: 387

CPU: i9-9900k

Cores: 8

GPU: RX580

iGPU: UHD 630

OC: No

Render frame size: FHD

HW Acc.: AMD

Encode mode: Intel QSV

Render As: Magix HEVC/AAC MP4 - Internet FHD 1080p 25 fps (Intel QSV)

Render time: 0:32 (only between the markers)

Render time: 0:51 (Full Project)

FPS: 9 average

===================================================================

Username: james-ollick

Machine: OB

VP version: 17

VP Build number: 387

CPU: i9-9900k

Cores: 8

GPU: RX580

iGPU: UHD 630

OC: No

Render frame size: UHD

HW Acc.: AMD

Encode mode: AMD VCE

Render As: Magix HEVC/AAC MP4 - Internet UHD 2160p 25 fps (AMD VCE)

Render time: 0:16 (only between the markers)

Render time: 1:35 (Full Project)

FPS: 9 average

====================================================================

Username: james-ollick

Machine: OB

VP version: 17

VP Build number: 387

CPU: i9-9900k

Cores: 8

GPU: RX580

iGPU: UHD 630

OC: No

Render frame size: FHD

HW Acc.: AMD

Encode mode: AMD VCE

Render As: Magix HEVC/AAC MP4 - Internet HD 1080p 25 fps (AMD VCE)

Render time: 0:12 (only between the markers)

Render time: 0:51 (Full Project)

FPS: 9 average

JN- wrote on 1/27/2020, 6:57 PM

@james-ollick Great set of results, just heading off to bed now, Dublin time. I'll update your results tomorrow if thats ok.

james-ollick wrote on 1/27/2020, 7:01 PM

Absolutely, glad to help.

JN- wrote on 1/27/2020, 7:08 PM

@james-ollick Just looking at your second set of results... Render frame size = FHD but your Render As = Magix HEVC/AAC MP4 - Internet UHD 2160p 25 fps (Intel QSV). Should that be internet hd 1080p?

Those are really fast render times! for a moment there I thought you were only rendering out region 1🤪.

james-ollick wrote on 1/27/2020, 7:23 PM

Yes, thanks for catching that, I edited my results above. 🙂

1 2 3 4 … 11

of 11