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

[bugzilla-daemon at webkit.org]

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

--- Comment #7 from Justin Michaud <justin_michaud at apple.com> ---
(In reply to tasnim from comment #6)
> We got help from v8 engineer who reported compiled wasm size of ~198MB for
> the wasm
> (https://readalong.google.com/wasm/wasm/simd/481866636_7/
> wasm_wrapper_release_simd.wasm) on arm architecture. Is there a way to do
> the same for webkit?
> 
> On my mac, if I start the web app on chrome, chrome's taskmanager (can be
> opened up via settings -> more tools -> taskmanager): reports ~500MB (refer
> attached chrome_memory). Safari on Mac via activity monitor for the same
> reports to be ~2GB (refer attached safari_memory).
> 
> Sorry, I wasn't able to clearly infer chrome tab's memory via activity
> manager. Any pointers on what more we can do to investigate memory usage on
> safari?

I see ~2GB in Chrome too? WebKit assigns the cost GPU process memory for a tab to the tab itself, so it can be confusing to compare.

I think opening Safari and Chrome with only one tab, and measuring the total footprint is probably the best way to measure this. If you want to be extra careful about fixed overhead from the browser app itself, you can open multiple instances of the site and measure the growth rate.

-- 
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/20230518/214eca68/attachment.htm>