Announcement

Collapse
No announcement yet.

GPU benchmarks

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

  • 3LP
    replied
    I'd be interested to see what would the 980 Ti do on the V2 benchmark if you have a chance to try

    Thanks
    Stan

    Leave a comment:


  • Guest
    Guest replied
    Dual GTX 980 Ti 52.7 seconds in V-Ray 3.20.02 using driver version 353.30. This was in the original benchmark scene.

    Click image for larger version

Name:	Dual 980Ti.jpg
Views:	1
Size:	73.1 KB
ID:	857941
    Last edited by ; 24-07-2015, 01:02 PM.

    Leave a comment:


  • savage309
    replied
    Just wanted to point that adding the V-Ray version with which the test is made is important. Even minor V-Ray versions can have different results (as is the case with 3.20.03 and 3.20.02).

    Leave a comment:


  • voltron7
    replied
    Thanks super!

    Leave a comment:


  • super gnu
    replied
    Autocorrect messed a few words there and edit isn't working...

    ok i edited! (and edited this) ive noticed that when i hit "edit" i often get a blank posting window (i.e. it forgets what ive already posted) so in order to edit rather than replace, i have to copy my text, and paste it into the edit window before editing.

    im sure this never used to happen..
    Last edited by super gnu; 02-07-2015, 04:08 AM.

    Leave a comment:


  • super gnu
    replied
    No actually 2x 3930k (at 4.5 ghz) are approximately equivalent to a gtx 670

    Those three together equal one titan x. So it's 4x 3930k (at 4.5) equal one titan x. Gpu is obviously far more powerful. But.. If you already have a cpu render farm, and are testing / using a small number of gpus for rt (a common scenario I recon) then you don't have to leave the farm idle when using rt. My particular little setup, the gpus and CPU capacity I gave are evenly matched. So the only way I can get a boost from rt (without upgrading) is to use opencl and combine.
    Last edited by super gnu; 02-07-2015, 04:06 AM.

    Leave a comment:


  • 3LP
    replied
    Ah ha, yes that's good to know.
    Put aside the fact that's SP2, it seems that 2 x 3930k is equal to 1 Titan X.

    Stan

    Leave a comment:


  • vlado
    replied
    Interesting Thanks for sharing.

    Best regards,
    Vlado

    Leave a comment:


  • super gnu
    replied
    interesting one: bechmark 1.0, gtx 670 4gb, 3.20.02

    cuda: 4m 39 secs.

    opencl, with 2x 3930k using intel opencl driver

    2m 3.8 secs.

    i had to play with the RPP and ray bundle size to get my cpu usage up on the slave.

    if youve got a mix of cpus and gpus (i.e. most of us) then i wouldnt write off opencl just yet.
    Last edited by super gnu; 19-06-2015, 01:10 PM.

    Leave a comment:


  • 3LP
    replied
    Awesome mate!
    Better than a Titan X

    Stan

    Leave a comment:


  • chris-x//
    replied
    EVGA GTX 980 Ti Superclocked / 11 min 18 secs / 353.06
    Not Bad !

    Leave a comment:


  • Booska
    replied
    I just ran it on my Quadro K5000 and got 6 min 32 secs.

    Leave a comment:


  • savage309
    replied
    I've update the results already. The test with the newer driver and M6000 is done on another machine running Windows. The Linux drivers seems to be lacking behind.
    The times ratio can be a bit tricky - to get from 8 to 4 takes as much effort as from 4 to 2 .

    Leave a comment:


  • 3LP
    replied
    Nice, you won about 10% there!
    So the M6000 and the Titan are really close to each other now, the difference is barely perceptible, 10 secs on a 11min render...

    Do you mind updating those infos on the gdoc spreadsheet? I guess the full 8 gpus are closer to the symbolic 1min render now.

    Well done for the additional column with the "times slower" ratio, didn't thought about that one but really handy

    Stan

    Leave a comment:


  • savage309
    replied
    M6000, 353.06, Windows, V-Ray 3.20.02 - 674s.
    Btw, we changed since 3.1 the way we ship V-Ray RT GPU so we could benefit from the speed ups that the new drivers can give (before you had to update driver *and* V-Ray), good to see that is working too.

    Leave a comment:

Working...
X