anyone else having issues? i select a file from the splashe screen and it’s like 20s before the first screen comes up, then it dranks through shader compilation real slow too. told be to increase the shader compilation thing, i knocked it up a bit but seems to have made no difference.
To speed up shader compilation, you can adjust the settings in max shader compilation subprocesses. 
Which file (ans size) and how is your system ? Does it have a lot of complex shaders…
You may have to elaborate this to get a more suited answer.
1 Like
file is 431mb and has been working no prob in 4.1.
had a bunch of shaders but none of them are complex w/ hundreds of connections etc.
quick rough time, from splash screen
4.1 - bout 8 seconds
4.2 - 68 secs. 30 just to get rid of the splash.
Because of the file size… and assuming windows… this could not be something like preread for one app because loaded already sometime and now reading anew because it’s another app (of course this would be a silly implmentation… but hey… it’s windows… 
) ??
( Long time on linux Debian her 
)
4.2 is slower.
He’s already comparing windows to windows, and it was working faster on 4.1.
4.2 has eevee next, which certainly does look better in most situations, but it requires more powerful hardware, in addition to being new and not fully polished.
2 Likes
That’s right.
Shader compilation is slow and consumes more memory.
We hope to improve this part in the future. 
1 Like
just to confirm, yes - Win 10, and i use Cycles.
i upped the shader compilation thing to 5, not sure what guidance there is about finding sweet spots etc.
It depends on the number of threads you have in CPU, (you can use them all if you want) but I think that has a lot more impact on Eevee, for me preview times (counting shader compilation) are much faster in cycles (and have not increased in 4.2/3), I now preview in cycles most of the time.
I have not found Cycles to be slower but I do not have files that large either.