Unity Web Stripping Tool Feedback

[Johannski]

Hey Marcel,

Thanks a lot for your thorough answer, this helps a lot! I took you settings and started some new builds (Which you can easily reproduce by using the Menu Item Tools->Build WebGL->minsize-stripping-webgl2). Here are the new results:

	Normal	Stripped
Demo	6000.1.11f1-minsize-webgl2 (2.93 MB)	6000.1.11f1-minsize-stripping-webgl2-v3 (2.85 MB)
Compressed wasm size	2.483.309 bytes (2.37MB)	2.404.593 bytes (2.29MB)
Uncompressed wasm size	9.233.180 bytes (8.80MB)	8.589.730 bytes (8.19MB)

so the reduction is ~600KB uncompressed and ~80KB compressed. I guess I was hoping for a bit more than 3% size reduction, but looking at the uncompressed size I can see that this is quite an improvement.

@MarcelPursche

What stripping settings did you use for testing? Did you also enable “Optimize Code After Stripping”? This options takes a while but it runs additional code optimization passes after the submodules are removed from the WebAssembly file, e.g., dead code removal, inlining, duplicate function merging. In my experience this will have a pretty significant impact on code size.

Overall the size savings of course highly depend on what Unity features your project is using and how well the existing code stripping features are able to work(Managed Stripping, compiler optimization). If you have a lot of code that can not be stripped by the other mechanisms you will see higher gains.

Yes, I was using Optimize Code after Stripping, here is the file I’m using.

Depending on what you are building the WebGL / WebGPU submodule will be added in the build script.

Since this is a project with very little custom user code. Do you have rough numbers for how e.g. a 10 MB compressed wasm file will change?

@MarcelPursche

I guess you are starting the editor in batch mode in your CI setup? I will try to reproduce this bug and log it. The StrippingProjectSettings.ActiveSettings are stored in the project settings and should be automatically set when the project is loaded. Maybe there is an issue with this mechanism in batch mode.

Yep exactly, running game.ci, you can see the workflow here. I also could imagine that the problem comes from the settings not being properly loaded. Side note: The settings file somehow duplicates the data and is not nice from a version control perspective (one line which is hard to read).

@MarcelPursche

How did you select the submodules to remove in your project? Did you use the submodule profiling feature of the package? This will automatically detect what submodules are unused during a profiling run and create a report that you can import back into the tool.

I tried it, but somehow got all modules listed as being strippable, therefore I didn’t try it any further, but maybe something else was off at that time