Performance mode

[deltakosh]

The goal is to protect backward compatibility but also offer an option for users to say they are ok to not be backward compatible (OR less easy to use) to favor perf by default

[sebavan]

Love it :-)

[azure-pipelines]

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

[deltakosh]

One thing I will do after merging this (when we are all ok with it) will be to document the consequences. What you will lose /have to pay to get to the best performance

[azure-pipelines]

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

[azure-pipelines]

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

[azure-pipelines]

Snapshot stored with reference name:
refs/pull/12954/merge

Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/12954/merge/index.html

To test a playground add it to the URL, for example:

https://babylonsnapshots.z22.web.core.windows.net/refs/pull/12954/merge/index.html#WGZLGJ#4600

Links to test babylon tools with this snapshot:

https://playground.babylonjs.com/?snapshot=refs/pull/12954/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/12954/merge
https://gui.babylonjs.com/?snapshot=refs/pull/12954/merge
https://nme.babylonjs.com/?snapshot=refs/pull/12954/merge

To test the snapshot in the playground with a playground ID add it after the snapshot query string:

https://playground.babylonjs.com/?snapshot=refs/pull/12954/merge#BCU1XR#0

[bghgary]

I like it. Do we want to maintain backwards compatibility when people set to Aggressive? I.e., if later, we decided that more things need to change for Aggressive mode, can we update it?

[deltakosh]

I like it. Do we want to maintain backwards compatibility when people set to Aggressive? I.e., if later, we decided that more things need to change for Aggressive mode, can we update it?

Nope, I will quote that in the doc. Aggressive is not backward compatible

[Popov72]

Nice!

[azure-pipelines]

Visualization tests for webgl1 have failed. If some tests failed because the snapshots do not match, the report can be found at

https://babylonsnapshots.z22.web.core.windows.net/refs/pull/12954/merge/testResults/webgl1/index.html

If tests were successful afterwards, this report might not be available anymore.