3 ms·

See the infamous story about Quack 3 on ATI Radeon cards.

• deaddodo 3y ago
  Here's the link, for those interested: https://techreport.com/review/how-atis-drivers-optimize-quake-iii/ https://techreport.com/review/how-atis-drivers-optimize-quak... Personally, I don't believe this is a good example; as this was ATI purposefully crippling the experience (downscaling textures, being the prime aspect) to cheat benchmarks. OP is more referring to "transparent" optimizations (the same experience, but made to run faster for the GPUs architecture, usually via operation reordering or shader modifications).
  • zten 3y ago
    Ah, yes, that's true, it's usually not done maliciously like the ATI example. It came to mind because it was a well-documented case of the driver being aware of the application and changing behavior.
    • account42 3y ago
      Newer APIs even have the program provide more detailed information [0] so workarounds can more easily apply to e.g. multiple games using the same engine. Renaming the executable won't be enough to test for / disable this kind of hack today. [0] https://registry.khronos.org/vulkan/specs/1.3-extensions/man/html/VkApplicationInfo.html https://registry.khronos.org/vulkan/specs/1.3-extensions/man...