Announcement

Collapse
No announcement yet.

RADV Lands VK_PIPELINE_CREATE_DISABLE_OPTIMIZATION_BIT

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

  • RADV Lands VK_PIPELINE_CREATE_DISABLE_OPTIMIZATION_BIT

    Phoronix: RADV Lands VK_PIPELINE_CREATE_DISABLE_OPTIMIZATION_BIT

    The RADV Vulkan driver within Mesa has landed its VK_PIPELINE_CREATE_DISABLE_OPTIMIZATION_BIT support so applications/games can opt to disable optimizations when compiling a Vulkan pipeline. This is notably what was just covered the other day for helping to reduce stuttering with DXVK...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Neat idea to trade some performance for reduced compilation time temporarily. How much does performance decrease when optimizations are off though?
    Last edited by shmerl; 13 May 2018, 10:02 AM.

    Comment


    • #3
      Originally posted by shmerl View Post
      How much does performance decrease when optimizations are off though?
      Right now the effects on both pipeline compile times and runtime performance are negligible, and while i'm working on merging my code into the main branch, it'll be disabled by default. As of right now, it's just not worth using.

      That said, Nvidia might eventually implement support for this flag as well.

      Comment


      • #4
        Originally posted by VikingGe View Post
        Right now the effects on both pipeline compile times and runtime performance are negligible, and while i'm working on merging my code into the main branch, it'll be disabled by default. As of right now, it's just not worth using.
        Are changes needed on your side or mesa to make it worth it?

        Comment


        • #5
          Originally posted by geearf View Post

          Are changes needed on your side or mesa to make it worth it?
          It appears that most of the time is spent inside the LLVM backend, but it's not trivial to speed that up so it doesn't sound like it will happen anytime soon.

          Comment


          • #6
            Originally posted by smitty3268 View Post

            It appears that most of the time is spent inside the LLVM backend, but it's not trivial to speed that up so it doesn't sound like it will happen anytime soon.
            Oh I see, another LLVM blocker :/

            Thanks!

            Comment

            Working...
            X