Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
|
|
Thread Tools | Search this Thread | Display Modes |
23rd April 2015, 14:16 | #1801 | Link |
Registered User
Join Date: Dec 2011
Posts: 1,812
|
With a GTX 980, I'm having a little higher GPU load with MPDN 64 neurons, compared to madVR (with the exact settings you have given).
With madVR, it's ~32% GPU usage when scaling 720p25 -> WQHD, with MPDN it's ~39%. The difference seems to get stronger when I additionally let both renderers downsample to maximized windowed resolution. In both players, render and presentation queues are set to 4 frames (new windowed path). I'm not giving much about render times since the GPU doesn't always run with the same clock. But, it's working without any glitches on a quick try. Will do quality comparisons as soon as I got more time. Very nice progress again! Edit: Could someone please explain again what the technical reason is why NNEDI3 via DirectCompute is much slower than via OpenCL? Last edited by aufkrawall; 23rd April 2015 at 14:33. |
23rd April 2015, 22:51 | #1802 | Link |
Registered User
Join Date: Jul 2013
Posts: 33
|
Code:
1) Amd 290 2)A 16/Scalar: 84%/534 Avg Render 10.50ms, 32/Scalar: 88%/564 Avg render 11.85ms, 64/Scalar: 83%/610 Avg Render 15.34ms, 128/Scalar: 100%/725 Avg Render 21.30ms, 256/Scalar: 100%/922 Avg Render 33.63ms DWM glitches present 84 2)B 16/vector: 67%/606 Avg Render 11.11ms, 32/vector: 72%/586 Avg Render 12.71ms, 64/vector: 85%/630 Avg Render 16.35ms, 128/vector: 90%/743 Avg Render 23.57ms, 256/vector: 100%/953 Avg Render 37.27ms DWM glitches present 221 2)C 16/branches: 84%/544 Avg Render 11.28ms, 32/branches: 80%/605 Avg Render 12.78ms, 64/branches: 81%/642 Avg Render 16.35ms, 128/branches: 96%/753 Avg Render 23.48ms, 256/branches: 100%/953 Avg Render 37.34ms DWM glitches present 229 3) 1280/720 24p 4) 1920x1059 5) Max Performance 2)A 16/Scalar: 67%/565Mhz Avg Render 11ms, 32/Scalar: 96%/574 Avg Render 12ms, 64/Scalar: 80%/630 Avg Render 15.65ms, 128/Scalar: 100%/720 Avg Render 21.42ms, 256/Scalar: 100%/923 avg render 33.72ms DWM glitches Present 68 2)B 16/vector: 80%/553mhz Avg Render 11.48ms, 32/vector: 62%/561 Avg Render 13.08ms, 64/vector: 81%/655 Avg Render 16.45ms, 128/vector: 100%/764 Avg Render 23.73ms, 256/vector: 100%/955 Avg Render 37.56ms DWM glitches present 127 2)C 16/branches: 72%/523 Avg Render 10.83ms, 32/branches: 95%/584 Avg Render 13.19ms, 64/branches: 98%/648 Avg Render 16.44ms, 128/branches: 100%/760 Avg Render 23.58ms, 256/branches: 100%/953 Avg Render 37.70ms DWM glitches present 203 5) Image Quality |
24th April 2015, 02:20 | #1803 | Link | ||
Suptitle, MediaPlayer.NET
Join Date: Nov 2001
Posts: 1,721
|
Quote:
Quote:
All these reports will be very handy to come up with automatic "path" selection. |
||
24th April 2015, 04:22 | #1804 | Link | |
Troubleshooter
Join Date: Feb 2014
Posts: 339
|
Avoid Branches
Quote:
Code:
1) Nvidia 680m GTX (Optimus system) 2) 16/Scalar: 24%/718.5Mhz(gpu)900mhz(mem) (render 12-13ms), 16/Vector: 22-17% gpu load (clocks remain the same as in other test) 11-12ms, 16/Branch: 22% gpu (render 11-12ms), 32/Scalar: 33% gpu (render 16ms), 32/Vector: 31% gpu (render 15ms), 32/Branch 30% gpu (render 15ms), 64/Scaler: 52% gpu (render 24ms), 64/Vector: 48% gpu (render 24ms), 64/Branch: 48% gpu (render 22ms), 128/Scalar: 94% gpu (render 64ms) in other words dropped frames and failure to be a worthwhile setting, 128/Vector: 92% gpu (render 62ms) in other words dropped frames and failure to be a worthwhile setting, 128/Branch: 84% gpu (render 36-37ms) - Actually worked!?! 3) 848x480 23p 4) 1920x1080 5) Image Quality
__________________
System specs: Sager NP9150 SE with i7-3630QM 2.40GHz, 16 GB RAM, 64-bit Windows 10 Pro, NVidia GTX 680M/Intel 4000 HD optimus dual GPU system. Video viewed on LG notebook screen and LG 3D passive TV. Last edited by Anime Viewer; 24th April 2015 at 04:37. |
|
24th April 2015, 04:29 | #1805 | Link |
Suptitle, MediaPlayer.NET
Join Date: Nov 2001
Posts: 1,721
|
If the driver does a good job at utilizing the GPU resource with any given shader code, you should get the same regardless of which option you choose. NV hardware seems to like the "Avoid Branches" path, and yes the difference could be massive like what you saw. Blame the driver!
|
24th April 2015, 04:46 | #1806 | Link | |
Troubleshooter
Join Date: Feb 2014
Posts: 339
|
Quote:
I feel like it would be slightly amusing if AMD turns out to work best with the third option (Scalar). Then each of the three vendor cards would work better with a different shader code.
__________________
System specs: Sager NP9150 SE with i7-3630QM 2.40GHz, 16 GB RAM, 64-bit Windows 10 Pro, NVidia GTX 680M/Intel 4000 HD optimus dual GPU system. Video viewed on LG notebook screen and LG 3D passive TV. Last edited by Anime Viewer; 24th April 2015 at 04:49. |
|
24th April 2015, 04:54 | #1808 | Link | |
Suptitle, MediaPlayer.NET
Join Date: Nov 2001
Posts: 1,721
|
Quote:
From Scyna's feedback, AMD seems to prefer scalar/vector depending on the neuron setting. Last edited by Zachs; 24th April 2015 at 04:59. |
|
24th April 2015, 05:10 | #1809 | Link | |
Troubleshooter
Join Date: Feb 2014
Posts: 339
|
Quote:
Edit: with the new drivers the scalar ms reading dropped slightly (from 190ms to 187ms), but vector still seemed to preform better with the Intel 4000. Maybe its an Optimus thing more than a 4000 thing, but regardless it doesn't matter since NNEDI3 is unusable with the 4000 anyway.
__________________
System specs: Sager NP9150 SE with i7-3630QM 2.40GHz, 16 GB RAM, 64-bit Windows 10 Pro, NVidia GTX 680M/Intel 4000 HD optimus dual GPU system. Video viewed on LG notebook screen and LG 3D passive TV. Last edited by Anime Viewer; 24th April 2015 at 05:20. |
|
24th April 2015, 05:14 | #1810 | Link | |
Suptitle, MediaPlayer.NET
Join Date: Nov 2001
Posts: 1,721
|
Quote:
Anyway, I've just found two other code paths that could make a difference, I'll add that and let you guys have a play. |
|
24th April 2015, 05:50 | #1811 | Link |
Registered User
Join Date: Mar 2009
Posts: 3,646
|
Same with nvidia. Intel HD graphics does better with Prefer Vector and considerably so.. Strange is that 64 neurons with Prefer Vector is twice as fast as 32 neurons set the same.. Any ideas why? In fact 64 neurons is faster than 16!
Last edited by ryrynz; 24th April 2015 at 06:00. |
24th April 2015, 05:56 | #1812 | Link | |
Suptitle, MediaPlayer.NET
Join Date: Nov 2001
Posts: 1,721
|
Quote:
My only very rough guess is that they do very specific optimizations for games and some conditions must've triggered it. On other cases, they couldn't be bothered. |
|
24th April 2015, 06:08 | #1813 | Link |
Registered User
Join Date: Mar 2009
Posts: 3,646
|
Thought something was fishy there.. It was the hd graphics not the 820 that was running. Surprising what works for one doesn't work so well for others and changing depending on neuron count... I think this should perhaps be able to be set individually per neuron count. Trying to do it automatically might not work too well.
|
24th April 2015, 06:14 | #1814 | Link | |
Suptitle, MediaPlayer.NET
Join Date: Nov 2001
Posts: 1,721
|
Quote:
|
|
24th April 2015, 07:10 | #1818 | Link | |
Suptitle, MediaPlayer.NET
Join Date: Nov 2001
Posts: 1,721
|
Quote:
|
|
24th April 2015, 07:37 | #1819 | Link |
Registered User
Join Date: Jul 2013
Posts: 33
|
Code:
1) Amd 290 2)A 16/Scalar small code: 88%/530 Avg Render 10.78ms, 32: 78%/575 Avg Render 12.14ms, 64: 87%/638 Avg Render 15.29ms, 128: 100%/717 Avg Render 21.17ms, 256: 100%/905 Avg Render 32.87ms DWM glitches present 13 2)B 16/vector small code: 78%/556 Avg Render 10.93ms, 32: 50%/610 Avg Render 12.96ms, 64: 93%/634 Avg Render 16.54ms, 128: 100%/749 Avg Render 23.18ms, 256: 100%/951 Avg Render 36.82ms DWM glitches present 259 3) 1280/720 24p 4) 1920x1059 5) Max Performance 2)A 16/Scalar small code: 59%/579 Avg Render 10.85ms, 32: 86%/589 Avg Render 12.62ms, 64: 80%/667 Avg Render 15.15ms, 128: 100%/734 Avg Render 21.41ms, 256: 100%/918 Avg Render 33.06ms DWM glitches present 6 2)B 16/vector small code: 61%/564 Avg Render 11.30ms, 32: 82%/596 Avg Render 13.02ms, 64: 81%/649 Avg Render 16.22ms, 128: 100%/743 Avg Render 23.48ms, 256: 100%/951 Avg Render 37.07ms DWm glitches present 251 5) Image Quality |
Tags |
direct3d, mpdn, nnedi3, opencl, reclock |
Thread Tools | Search this Thread |
Display Modes | |
|
|