a-b-street/abstreet

Web client performance

Open

#377 创建于 2020年11月3日

在 GitHub 查看
 (11 评论) (0 反应) (0 负责人)Rust (6,779 star) (256 fork)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
议题类型
performance
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
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.