[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 #9 from tasnim <tasnimrock2k6 at gmail.com> ---
(In reply to Justin Michaud from comment #7)
> (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.
Interesting: I have done a number of retries by opening via single tab and don't see that big a number on chrome. Maybe that's because I am looking at the chrome's taskmanager and you might be looking at activitymonitor?
> 
> 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.
I gave a shot on this to measure the growth rate:

Initially: total memory used via activity monitor: 14.40 GB
when site opened on first tab on chrome: 15.20 GB - (~800MB growth)
when same site opened on second tab on chrome: 15.90 GB - (~700 MB growth)
when site opened on third tab on chrome: 16.6 GB - (700 MB growth)

Same for safari when initial reported was 14.1 GB:
site opened on first tab: 16.70 GB (~2.6GB growth)
site opened on second tab: 19.3 GB (~2.6 GB growth)
safari reported: 22 (~2.7 GB growth) 

So, on my 3 attempts chrome is reporting a growth of 700-800 MB vs safari reporting ~2.6-2.7 GB.

-- 
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/f857575b/attachment.htm>