Profiling Shader.CreateGPUProgram

Hi,

can someone give me a clue on what Shader.CreateGPUProgram does?
The name seems self-explanatory but i actually don't get it, and why are multiple calls issued?

 

I wish to know about this also?

 

I think the way to optimize CreateGPUTime is:

1. go in Graphics, press Clear
2. run a few levels of the game in the editor
3. Graphics variant count went up
4. Save to assets then drop that Variant asset in the preloaded shaders array

correct?

 

I've been trying to optimize our async level loading times and one of the profiling issues I've recently encountered is the Shader.Parse call (which leads to the shader gpu programs stall).

Our setup uses asset bundles to load assets and scenes which seems to invalidate the regular shader preload technique (because the materials in the bundles refer the bundled shaders, not the ones baked into the ShaderVariantCollection added to the player graphics preload slot). So i've replaced that with a "manual" warmup that is done by our loader scene, so basically it warms up the same shadervariantcollection asset, but which is now baked into the bundles. Note that the shader collection is a complete level gather of shaders (according to the Unity built-in tracking system).

The problem is that I'm still getting those shader parsing spikes which makes me wonder how is that possible with the shader variants being already warmed up?

 

If for this problem, ShaderVariantCollection is a solution then can you guide me further into this?
How to use ShaderVariantCollection within the game or setup?

 

Any ideas why it would be taking up 97% of our project startup time?

 

unity version ?
2020.3 and above has regressed massively with up to 70% slowdown, if that's the case log a bug and report in this thread as well as the 21.2 alpha to prioritize fix

 

This is in 2020.3.2 (you guessed it). We upgraded from 2019.3.0. Our team is reverting back to 2019 but I'll be sure to link the bug report in multiple places if I file one. The only thing blocking me from reporting a bug is the thought of stripping down our project. Do you think that's necessary?

 

not in cases like these - they need real life projects

 

@Ryan_McMahon The same happened to me on android when using new Texture2DArray();