Results 1 to 5 of 5

Thread: NVIDIA Puts Out 290 Linux Driver Series Beta

  1. #1
    Join Date
    Jan 2007
    Posts
    14,912

    Default NVIDIA Puts Out 290 Linux Driver Series Beta

    Phoronix: NVIDIA Puts Out 290 Linux Driver Series Beta

    It was just in August that NVIDIA was pushing out driver betas for their Linux/Solaris/FreeBSD 285.xx series, but now that the series is stable, they have moved onto the 290.xx series. On Friday NVIDIA released the 290.03 Linux driver beta...

    http://www.phoronix.com/vr.php?view=MTAwNDU

  2. #2
    Join Date
    Oct 2009
    Posts
    353

    Default

    The cached shaders don't need to be compiled after starting a GL app. After the app is started there's no runtime difference between cached & non-cached shaders, so I wonder how/why would one benchmark cached vs non-cached shaders?

  3. #3

    Default

    Quote Originally Posted by cl333r View Post
    The cached shaders don't need to be compiled after starting a GL app. After the app is started there's no runtime difference between cached & non-cached shaders, so I wonder how/why would one benchmark cached vs non-cached shaders?
    I cannot imagine a graphics driver that did not cache such things in memory in the first place, so the advantage of caching shaders on the disk would be to keep them available between runs. If there is an option to disable it, Michael could use thta. Otherwise, he could just wipe the cache.

  4. #4
    Join Date
    Nov 2008
    Location
    Madison, WI, USA
    Posts
    874

    Default

    Quote Originally Posted by cl333r View Post
    The cached shaders don't need to be compiled after starting a GL app. After the app is started there's no runtime difference between cached & non-cached shaders, so I wonder how/why would one benchmark cached vs non-cached shaders?
    How:
    1) Delete shader cache contents
    2) Run a single timedemo run in the game being benchmarked (not 3 runs)
    3) Repeat steps 1 and 2 for as many runs as you want

    Why:
    Allows you to see how much of a loading bottleneck the shader compiler is. I have done the same thing in the OpenCL programs that I am working on. Caching compiled OpenCL kernels instead of compiling them each run saves about 0.5 - 0.75 seconds of startup time for me. This could save a second or so on each level load in the game of your choice.

  5. #5
    Join Date
    Sep 2007
    Location
    Connecticut,USA
    Posts
    962

    Default

    I have tested the 290.03 x86_64 and x86 versions and they cause Flash to crash frequently...which means Flash does not handle this driver well...oh well!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •