Commen=
t # 12
on bug 97879<=
/a>
from Michel D=C3=A4nzer
(In reply to Andreas Hartmetz from comment #4)
> Assuming the problem was shader compilation, wha=
t could be done about it,
> though? Optimizing shader compilation by a factor of 10 seems unrealis=
tic,
Not necessarily. Let's worry about that once the code taking so much time is
identified and analyzed. For that purpose, what's needed next is CPU profil=
es
of the stalls.
> a disk cache for shaders has been rejected (righ=
t?)
No, it hasn't.
> and would not always help, e.g. when somebody wi=
th a car that uses a new
> asset joins.
Right, there's only so much the driver stack can do when the game (engine)
keeps compiling shaders.