Announcement

Collapse
No announcement yet.

GPU benchmarks

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

  • savage309
    replied
    1080 is a very good GPU, but it is a replacement for 980, not for the Titan X. It is quite faster than the 980 and has more RAM, and fast as Titan X, which is great.
    With the new drivers I hope there to be some improvement as well, but I don't think it will get much faster than it is today.
    Btw, teraflops should be compared only between the same architectures, otherwise they don't mean too much.

    Best,
    Blago.

    Leave a comment:


  • Sushidelic
    replied
    I can confirm that 1080's performance is pretty much the same as a TitanX right now. Waiting and hoping for Cuda8 to hit the streets in new drivers, squeezing the last out of the Pascals. 1080 should be ~150% of a TitanX if you look at raw Teraflops only.Click image for larger version

Name:	whynot.jpg
Views:	1
Size:	502.2 KB
ID:	862550
    Last edited by Sushidelic; 05-07-2016, 10:02 AM.

    Leave a comment:


  • Morne
    replied
    Would love to see how AMD's 480 does with this...

    Leave a comment:


  • FSGFX
    replied
    Vlado did some tests on google+
    https://plus.google.com/+VladimirKoy...ts/R1XPacoWvB4

    Leave a comment:


  • werticus
    replied
    Still no one with a 1080? Common :P

    Leave a comment:


  • savage309
    replied
    Originally posted by tricky View Post
    I've downloaded the scene from the link on the spreadsheet. The render just keeps on going. Should it stop at 2048 paths/pixel? Its currently at 2688 paths/pixel and still going.
    There are two benchmarks. 1.0 and 2.0.
    1.0 should run in less than 2 minutes, the other one in less than 20 minutes with your GPU.
    There are links for downloading both of them in the spreadsheet. Keep in mind that between different V-Ray versions the time may vary a lot. For the same amount of pixels it gives the different noise level, etc.
    V-Ray 3.30 and later can do a bit more paths per pixel than the specified in the settings, so this is normal as well.

    Leave a comment:


  • tricky
    replied
    I've downloaded the scene from the link on the spreadsheet. The render just keeps on going. Should it stop at 2048 paths/pixel? Its currently at 2688 paths/pixel and still going.

    Leave a comment:


  • tricky
    replied
    Originally posted by savage309 View Post
    I think you are not starting the correct test. Do you have log / from where you got the scene ?
    Best,
    Blago.
    I think I must have the wrong scene. Can you give me a link to download the correct one please?

    (EDIT - Ah. I think I've found it)
    Last edited by tricky; 16-06-2016, 01:10 AM.

    Leave a comment:


  • savage309
    replied
    I think you are not starting the correct test. Do you have log / from where you got the scene ?
    Best,
    Blago.

    Leave a comment:


  • tricky
    replied
    Click image for larger version

Name:	Standard.jpg
Views:	1
Size:	87.8 KB
ID:	862410
    My render dialogue tells me this took 2:43 to render and this is on a GTX980Ti and the latest drivers. Its good, but looking at the list of other cards, shouldn't I be expecting faster times?

    I am on 3.40.01 on Max2016. I notice a couple of missing texture maps when I open the scene, but other than that, I just switched to CUDA and clicked render

    Leave a comment:


  • DPGrafik
    replied
    Cool i'll look into it. Can't wait to see how this stack up against the i7 render nodes i have now.

    Leave a comment:


  • savage309
    replied
    Originally posted by DPGrafik View Post
    Sure thing - The eGPU will be up and running within two weeks, thats when i expect that final parts to arrive. It will be interesting to see both if it works and if it's significantly slower than internal GPU due speed limitations with connection. I'm using thunderbolt 2 to connect, so theoretically it should do 20GB/s but i think i read somewhere that with pci-e over thunderbolt 2 its limited to 5Gb/s, what that means for rendering we'll see once its running .
    RT GPU can be tuned for that. If you increase ray bundle size / rays per pixel, bigger chunks of work will be given to the GPUs, this will keep them more busy and will reduce the traffic (CPU to GPU and/or between DR nodes). This will reduce the interactivity a bit though. We have that pretty well documented here.

    Leave a comment:


  • DPGrafik
    replied
    Sure thing - The eGPU will be up and running within two weeks, thats when i expect that final parts to arrive. It will be interesting to see both if it works and if it's significantly slower than internal GPU due speed limitations with connection. I'm using thunderbolt 2 to connect, so theoretically it should do 20GB/s but i think i read somewhere that with pci-e over thunderbolt 2 its limited to 5Gb/s, what that means for rendering we'll see once its running .

    Leave a comment:


  • savage309
    replied
    Originally posted by DPGrafik View Post
    I'm building a eGPU setup as a test to see if it's viable. And then i'm building a linux/windows machine with GTX 1080's to use as a DR render. I've been told by you guys that as long as i use a machine with another OS via DR it shouldn't be a problem.
    Cool! I would like if you can share how it went once it is up and running.

    Best,
    Blago.

    Leave a comment:


  • DPGrafik
    replied
    I'm building a eGPU setup as a test to see if it's viable. And then i'm building a linux/windows machine with GTX 1080's to use as a DR render. I've been told by you guys that as long as i use a machine with another OS via DR it shouldn't be a problem.

    Leave a comment:

Working...
X