Here is with TDR disabled, no crashes. 980 TI driver 355.82
Sorry to ask but did you restart your computer after the change?
Seems we have a divergence to that of PadyEOS who also has a 980TI
Cheers
Here is with TDR disabled, no crashes. 980 TI driver 355.82
Hi, I've created an account just because ToTTenTranz asked for more Maxwell results with CPU usage.
Here's my perf log on a 980 TI. I got a TDR crash on the single commandlist but it shouldn't matter.
Also, here is overall CPU usage on the duration of the test on a i7 5960X:
View attachment 866 View attachment 867 View attachment 868
Sorry to ask but did you restart your computer after the change?
Seems we have a divergence to that of PadyEOS who also has a 980TI
Cheers
What Nvidia driver version did he use?
OK that possibly explains the divergenceYes, but to be perfectly honest I didn't completely disable TDR. I just increased the delay to 10 seconds so the test wouldn't crash.
970 on 355.82 OCed. Didn't get a TDR. Also attached is Afterburner log if anyone is interested.
OK that possibly explains the divergence
Can you do the test with actually disabling it like PadyEOS did?
Cheers
Are you basing PadyEOS results from page 12?So with nVidia Maxwell 2, specifically a GM200 Geforce 980 Ti we have 2 different results so far:
1 - Async exists somehow but it causes a huge load on the CPU -> PadyEos' result using 355.82
2 - Async doesn't exist at all -> Devnant's result using 355.82 too...
I wonder what's causing this "CPU-assisted Async" to kick-in.
If it was pure CPU performance, then it should be Devnant's machine the one to activate Async, since his CPU has twice the cores/threads.
Perhaps CPU frequency?
ToTTenTranz,
look at around thread 200 to say 265 (happens in other places).
You agree it shows Compute+render time is consistently less than the individual runs of Compute and Async?
So how is this possible serially?