[Webkit-unassigned] [Bug 256703] [iOS] Wasm based WebApp readalong.google.com reproducibly jetsams

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Jun 22 23:06:39 PDT 2023


https://bugs.webkit.org/show_bug.cgi?id=256703

--- Comment #37 from tasnim <tasnimrock2k6 at gmail.com> ---
(In reply to Justin Michaud from comment #36)
> I have looked further into this.
> 
> 150mb - wasm tables, element sections, as you previously identified. 
> - We need to optimize this so that we don't need to generate so many wasm to
> js wrappers, and so that we can collect them. There is no ETA on that, but
> we know we need to do it.
> 
> WORKAROUND: don't put functions in tables if they aren't used, and don't put
> data in element sections if it isn't used.
> 
> 60mb - Interpreter bytecode
> 120mb - JIT memory
> 
> We should be able to collect these before you jetsam, and we have a separate
> bug about that. We know we need to do that.
> 
> WORKAROUND: try building with Os if you aren't already, and measuring if
> that meets your performance needs.
We are already build with Oz. Seems this is the best we could do in terms of reducing code size: https://emscripten.org/docs/tools_reference/emcc.html#emcc-oz
> 
> Thank you for filing this bug. This is a super helpful test case.
> 
> I was not able to find a single smoking gun that explains the memory usage
> difference, but rather many small wasm memory inefficiencies. I will try to
> work on these in the future, but unfortunately that leaves nothing
> actionable for you right now. If you can reduce the size of your wasm Table
> and Memory, then perhaps you can get under the jetsam limit. 
> 
> The non-wasm version seemed pretty usable and used substantially less
> memory, so if shipping that is an option for now, that might be the fastest
> fix on your end while we work to improve our wasm memory usage in future
> releases.
> 
> I will come back to this bug from time to time to update you on any
> improvements that land.
Awesome, Thanks!

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230623/d68bb71c/attachment.htm>


More information about the webkit-unassigned mailing list