# OPTIMIZE YOUR SHADERS!

Shaders are basically mathematical operations, and everyone knows that conditional statements are not shader friendly, and yeah, we can overcome then by basically turning then into math!

See this use case:

`if (x == 10) {`

` value += 1;`

`}`

instead of this condition when can do:

`value += 1 * when_eq(x,10);`

In the above example the when_eq will return only 0 or 1, 1 only when x is 10 that means that value will increased by 0 when x not equal 10. Quite simple dont you think?

##### Shader code

```
// Those snippets are in vec4 type but you can change to another types like:
// vec3, vec2, float, int ..........
vec4 when_eq(vec4 x, vec4 y) {
return 1.0 - abs(sign(x - y));
}
vec4 when_neq(vec4 x, vec4 y) {
return abs(sign(x - y));
}
vec4 when_gt(vec4 x, vec4 y) {
return max(sign(x - y), 0.0);
}
vec4 when_lt(vec4 x, vec4 y) {
return max(sign(y - x), 0.0);
}
vec4 when_ge(vec4 x, vec4 y) {
return 1.0 - when_lt(x, y);
}
vec4 when_le(vec4 x, vec4 y) {
return 1.0 - when_gt(x, y);
}
//Here are some logical operators to use with the results from above:
vec4 and(vec4 a, vec4 b) {
return a * b;
}
vec4 or(vec4 a, vec4 b) {
return min(a + b, 1.0);
}
vec4 xor(vec4 a, vec4 b) {
return (a + b) % 2.0;
}
vec4 not(vec4 a) {
return 1.0 - a;
}
```

Thanks for sharing, if you have any further tips and knowledge would you consider creating a cheat sheet git page?

-Nevermind I found the link ðŸ™‚

“everyone knows that conditional statements are not shader friendly” – not always. On desktop, if all the threads in a warp take the same branch, the branch doesn’t hurt you. On mobile (and desktop), if all threads in one dispatch or draw take the same branch, the branch doesn’t hurt you much either. You can use branches to skip parts of the shader and decrease overall execution time. Better to profile your shaders and see if the branches are an actual issue rather than just blindly avoiding them imo