Announcement

Collapse
No announcement yet.

GPU benchmarks

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • auke
    replied
    Hmm that is odd, in P0 the memory should be at 7000Mhz. I would also doubt setting P0 and P2 memory clocks to 4000 will give me back the lost 40% of performance. I suspect the problem then lies in the presence of a K4000 in the system as well or the reduced PCIe lanes per card (although I doubt this as going from x16 to x8 doesn't even make a noticable difference in most games.) Could you check the status of your PCIe interface? NVinspector tells me it is at "3.0 @ 2.0 x16. Thanks

    Leave a comment:


  • super gnu
    replied
    Cuda tasks always use P2 power state on maxwell. its a driver "feature" to guarantee stability for hpc workloads. ive asked Chaos if there is a way to get around it. thats not the issue for you , as all the maxwell cards have the same handicap.. i dunno about the other chips.

    having said that, you say your memory clock is cut in half? Thats much more extreme than ive found on my titan x (bog standard "cheapo" gainward) . mine goes from 3300 mhz in P0 state, down to 3000 mhz in P2.. hardly the end of the world.

    you can easily get around any clock throttling with NVinspector. set your P0 and P2 memory clock speeds to the same value (4000 mhz in my case) and watch vray fly.

    Leave a comment:


  • AlexP
    replied
    Originally posted by auke View Post
    Keep us updated! Very curious how it will work out, also what kind of trouble are you having with the ASUS board (and which one are you using)?

    Also a question for those using maxwell (gtz 9xx, Titan-X or M6000) cards. Could you please check what P-state your gpu's are in while rendering? It seems mine is stuck at P2 which halves the memory clockspeed, meanwhile I get benchmarks 40% lower than what I should expect looking at the benchmarks here.
    How do I find out what P-state?

    Leave a comment:


  • auke
    replied
    Keep us updated! Very curious how it will work out, also what kind of trouble are you having with the ASUS board (and which one are you using)?

    Also a question for those using maxwell (gtz 9xx, Titan-X or M6000) cards. Could you please check what P-state your gpu's are in while rendering? It seems mine is stuck at P2 which halves the memory clockspeed, meanwhile I get benchmarks 40% lower than what I should expect looking at the benchmarks here.

    Leave a comment:


  • 3LP
    replied
    Not yet, I'm still working on it
    I ordered a new riser that should fix my issue as it's the best one available, should be there next week, and it we will see.
    If it doesn't then I don't know how to make it work beside changing the motherboard, and man, I hate Asus boards, I should have gone for Asrock, those never let me down.

    Stan

    Leave a comment:


  • AlexP
    replied
    Nice

    All on one board?

    Leave a comment:


  • 3LP
    replied
    7 x Titan X OC - Benchmark 2.0 : 1m33.4 (did it twice to be sure )
    I wanted to get a rig that was equivalent but cheaper than the VCA, seems the challenge is done

    Click image for larger version

Name:	SNAG-0017.jpg
Views:	1
Size:	213.3 KB
ID:	858378

    Stan

    Leave a comment:


  • auke
    replied
    Hmm, just did a test run here on a Titan X and only getting 18 min and 10 seconds. I also notice an average of 1800 kpaths/s. Seems like the performance is practically split in half looking at the graphs. Could this be caused by my rig running a Quadro (K4000) and Titan X at the same time? The Quadro was not rendering though and I'm running GTX drivers. Running it all on 3ds Max 2016 and Vray RT 3.20.02.
    Last edited by auke; 22-09-2015, 01:49 AM.

    Leave a comment:


  • AlexP
    replied
    Originally posted by eyepiz View Post
    Odd...

    I ran (4) Original Titans at 28.04 sec.

    http://forums.chaosgroup.com/showthr...335#post579335
    Would different manufacturers make a difference? Mine was on Max 2015 also?
    No idea

    Leave a comment:


  • eyepiz
    replied
    Originally posted by AlexP View Post
    4 x Titan X - 30s
    [ATTACH=CONFIG]26019[/ATTACH]

    edit:

    8 X Titan X = 14s

    Think maybe the scene is "too easy" to test with more power?
    Odd...

    I ran (4) Original Titans at 28.04 sec.

    http://forums.chaosgroup.com/showthr...335#post579335

    Leave a comment:


  • cray-zard
    replied
    nope its just a zotac 980ti ref..

    Leave a comment:


  • super gnu
    replied
    Originally posted by cray-zard View Post
    [ATTACH=CONFIG]26048[/ATTACH]

    heres mine.. benchmark 2.0

    rendered in single 980ti.. 9:55
    Wow that's faster than a titan X. Is it overclocked ?

    Leave a comment:


  • cray-zard
    replied
    Click image for larger version

Name:	980tiref.jpg
Views:	1
Size:	430.3 KB
ID:	858369

    heres mine.. benchmark 2.0

    rendered in single 980ti.. 9:55

    Leave a comment:


  • AlexP
    replied
    Originally posted by 3LP View Post
    Use benchmark 2.0, it has been designer to suit bigger GPU systems :
    https://docs.google.com/spreadsheets...A0k/edit#gid=0

    Should take about 1min to render with your 8 Titan X.
    By the way, do you DR to get the 8 Titan X working? If so, from your wrkstn to the two nodes or from one node DR to the other?

    Stan
    4 in my workstation, and 4 in another.

    Ill check out the benchmark 2, will also test with 12 Titan X, out of interest.

    So far seems to scale quite linearly I guess

    Leave a comment:


  • 3LP
    replied
    Originally posted by AlexP View Post
    4 x Titan X - 30s
    [ATTACH=CONFIG]26019[/ATTACH]

    edit:

    8 X Titan X = 14s

    Think maybe the scene is "too easy" to test with more power?
    Use benchmark 2.0, it has been designer to suit bigger GPU systems :
    https://docs.google.com/spreadsheets...A0k/edit#gid=0

    Should take about 1min to render with your 8 Titan X.
    By the way, do you DR to get the 8 Titan X working? If so, from your wrkstn to the two nodes or from one node DR to the other?

    Stan

    Leave a comment:

Working...
X