Reduce page load times of web-UI

[mbfm]

Our web-UI is starting to require a relatively large download upfront for the WASM binary. The size of the WASM binary can be optimized by adapting the steps here: https://book.leptos.dev/deployment/binary_size.html

Mind that we have a CSR application, not SSR. We do not use cargo-leptos. We do not use the nightly compiler. The "Code Splitting" section also looks like it cannot be applied to our codebase, since we do not use server functions.
I would recommend focusing on steps 2 and 3 in the "Things to Do" section for now (modifying the release profile to optimize for speed and then ensuring we use compression for serving the WASM file in CARL).

You can test the size of the WASM binary by running cargo lea --release and then checking the "Network" tab in your browser developer tools for the WASM binary's download size.

[kKdH]

Hey guys, is it possible that we bloated the binary by pulling in unwanted dependencies?

e.g.:
opendut-lea -> opendut-auth -> tonic -> tokio-stream -> tokio

[mbfm]

Ah, good catch. The tonic dependency was not marked as optional = true on opendut-auth, which caused it to be included for LEA, too. I fixed this here: 1a24312

I also realized that the binary size may have grown quite a bit recently, when I upgraded our codebase to reqwest v0.13, while leptos_oidc still depends on v0.12, which means we currently pull two versions of reqwest and its transitive dependencies into LEA.
Might be worth opening a pull request at leptos_oidc to upgrade to the new reqwest version.

[kKdH]

hm...i think tonic isn't optional for the public client (lea). 🙈

error[E0433]: failed to resolve: use of unresolved module or unlinked crate `tonic`
 --> opendut-auth/src/public/mod.rs:4:5
  |
4 | use tonic::service::Interceptor;
  |     ^^^^^ use of unresolved module or unlinked crate `tonic`
  |

[kKdH]

Also, another "top ten" code size offenders is broti which we use for compression of setup-strings.

But we use brotli from day one, so i dont know if it makes sens to replace it with some other compression library.

[mbfm]

hm...i think tonic isn't optional for the public client (lea). 🙈

error[E0433]: failed to resolve: use of unresolved module or unlinked crate tonic
--> opendut-auth/src/public/mod.rs:4:5
|
4 | use tonic::service::Interceptor;
| ^^^^^ use of unresolved module or unlinked crate tonic
|

Ah, my bad. I guess, I didn't build with the right feature flags. The official example for authentication also uses the types from tonic, so I don't think we can get around it being included: https://github.com/hyperium/tonic/blob/master/examples/src/authentication/client.rs

Looks like we also need it in opendut-carl-api, though, so we wouldn't get rid of it anyways:

cd opendut-lea/ && cargo tree --invert=tonic --edges=features

tonic v0.14.3
├── opendut-auth v0.10.0-alpha (/home/fmaerkl/Projects/openDuT/repos/opendut/opendut-auth)
│   ├── opendut-auth feature "default"
│   │   ├── opendut-carl-api v0.10.0-alpha (/home/fmaerkl/Projects/openDuT/repos/opendut/opendut-carl/opendut-carl-api)
│   │   │   ├── opendut-carl-api feature "codegen"
│   │   │   │   ├── opendut-carl-api feature "default"
│   │   │   │   │   └── opendut-lea v0.10.0-alpha (/home/fmaerkl/Projects/openDuT/repos/opendut/opendut-lea)
│   │   │   │   │       └── opendut-lea feature "default" (command-line)
│   │   │   │   └── opendut-carl-api feature "wasm-client"
│   │   │   │       └── opendut-lea v0.10.0-alpha (/home/fmaerkl/Projects/openDuT/repos/opendut/opendut-lea) (*)
│   │   │   ├── opendut-carl-api feature "default" (*)
│   │   │   ├── opendut-carl-api feature "opendut-auth"
│   │   │   │   └── opendut-carl-api feature "wasm-client" (*)
│   │   │   └── opendut-carl-api feature "wasm-client" (*)
│   │   └── opendut-lea v0.10.0-alpha (/home/fmaerkl/Projects/openDuT/repos/opendut/opendut-lea) (*)
│   └── opendut-auth feature "public_client"
│       └── opendut-lea v0.10.0-alpha (/home/fmaerkl/Projects/openDuT/repos/opendut/opendut-lea) (*)
│       └── opendut-carl-api feature "wasm-client" (*)
├── opendut-carl-api v0.10.0-alpha (/home/fmaerkl/Projects/openDuT/repos/opendut/opendut-carl/opendut-carl-api) (*)
├── tonic-prost v0.14.3
│   └── tonic-prost feature "default"
│       └── opendut-carl-api v0.10.0-alpha (/home/fmaerkl/Projects/openDuT/repos/opendut/opendut-carl/opendut-carl-api) (*)
└── tonic-web-wasm-client v0.8.0
    └── tonic-web-wasm-client feature "default"
        └── opendut-carl-api v0.10.0-alpha (/home/fmaerkl/Projects/openDuT/repos/opendut/opendut-carl/opendut-carl-api) (*)
└── tonic feature "codegen"
    └── opendut-carl-api feature "codegen" (*)

[mbfm]

Also, another "top ten" code size offenders is brotli which we use for compression of setup-strings.

But we use brotli from day one, so i dont know if it makes sens to replace it with some other compression library.

I believe, there's no reason why we couldn't move the compression into CARL, so that there's a backend API which simply serves a brotli-encoded string. We would also need to adjust CLEO then.

But yeah, I would prefer to tackle lower-hanging fruit for now and see where we land with that...

[sdv-infy]

Hello @mbfm, Can you please assign this to me. I'd like to work on this.