<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Mesa 10.6.3 linker is slow" href="https://bugs.freedesktop.org/show_bug.cgi?id=91857#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Mesa 10.6.3 linker is slow" href="https://bugs.freedesktop.org/show_bug.cgi?id=91857">bug 91857</a> from <a class="email" href="mailto:CliveMcCarthy@gmail.com" title="Clive McCarthy <CliveMcCarthy@gmail.com>"> Clive McCarthy</a> <pre>(In reply to Tapani Pälli from <a href="show_bug.cgi?id=91857#c8">comment #8</a>) > Thanks for attaching the shader, will do some profiling on this later. > > In case this is a 'real life' case and you are having problem with this: > while this all is 'legal', IMO it would make more sense to write multiple > shaders for different purposes and then minimize state changes by grouping > the objects for rendering pass (a lot of apps and games do this). This will > likely result in better performance on any given platform compared to a > 'über-shader' approach. > > What comes to 'apples and oranges' comparison, on Nvidia you will need to > measure without shader cache. According to documentation below you should > either remove '$HOME/.nv/GLCache' or export __GL_SHADER_DISK_CACHE=false > before measuring (don't know if these work because docs seem a bit old): > > <a href="http://us.download.nvidia.com/XFree86/Linux-x86/319.32/README/">http://us.download.nvidia.com/XFree86/Linux-x86/319.32/README/</a> > openglenvvariables.html > > Then the comparison should be more fair. The shader itself is fast enough and works just fine (weird as it might be). The speed issue is with the Mesa linker, running x86 code. My über-shader allows me to try various approaches and experiment very quickly. The timing of the linker was done with gettimeofday() and represents how long the linker took before any rendering even began. This is not a rendering problem.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>