Yannick

Ok but is it a good idea to cache shader parameters? Because I can have a shader instance per material with 3 parameters changed per frame instead of all parameters. Don't know how @MonoGameTeam handle that internally.

There's no way to share cached uniforms across shaders, if that's what you're asking.

could you use structured buffers to pass params across shaders, like with compute?

No, MG does not expose it like that. Things like that have been discussed a long time ago, but we can't support it with the current shader pipeline.

Ok so using a cloned shader with parameters set one time is the same than the same shader used by multiple materials where parameters are updated very often?

Ah, I misunderstood. They're not the same. I think using 1 shader is faster. I would be interested to know!

But with only one shader you've to push data at each frames. So textures, etc... Not sure if it's good or not. I would say it's not good but I don't know that's why I ask

Textures in MG are stored in VRAM only, so it's not like the whole thing is uploaded every time you switch. Like I said, I'm not sure which way is faster.