a-b-street/abstreet

Web client performance

Open

#377 opened on 2020年11月3日

GitHub で見る
 (11 comments) (0 reactions) (0 assignees)Rust (6,779 stars) (256 forks)batch import
good first issue

説明

Some different ideas for smoothing out the web client:

  • The .wasm binary is around 50MB, which makes initial startup time quite sad. Gzipped is around 20MB. I can't find any option to enable this in wasm-pack, because I think people generally just configure their web servers to do compression on-the-fly if the HTTP client sends Accept-Encoding headers. S3 doesn't support this, but I think it's possible to upload a .wasm.gz, point to it from the .html, and set the Content-Encoding header properly. Just need to test this and make sure browsers understand it.
  • Keep the Scenario for the current map in memory after loading it from a file. Otherwise, everytime the player resets to midnight in many gameplay modes, they have to download the file again!
  • In wasm_loader::FileLoader, display a progress bar with bytes downloaded / total length. I found set_onprogresss for XmlHttpRequest, but actually, we're currently using web_sys::Request, which is different. Can we switch?

コントリビューターガイド

技術スタック
rustwasmhtmlcss
領域
frontendperformance
Issue 種別
performance
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
basic Rustweb assembly knowledgeweb development basics
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
55
調査方針
Investigate wasm pack options for gzip compression of .wasm files, and test serving .wasm.gz with Content Encoding header. For caching, modify the Scenario loading logic to persist the loaded scenario in memory after initial file load. For progress bar, explore switching from web sys::Request to XmlHttpRequest (or use fetch with progress events) in wasm loader::FileLoader, and consult MDN for progress event implementation.