[Webkit-unassigned] [Bug 218939] Consider AoT-compiling small (<64KB?) WebAssembly Modules immediately without interpreting?

[bugzilla-daemon at webkit.org]

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

--- Comment #3 from jujjyl at gmail.com ---
I guess the rationale for this might be for when people write really small synthetic benchmarks that run synchronously.

E.g. maybe wasm counterparts of https://jsben.ch/ or https://jsbench.me/ types of pages.

Or otherwise when one is testing how some small thing X works.

In the example of t_shapes_looped.html, I was originally writing a test case in a programming contest where performance of the code was measured. I was getting bad time results with Safari, before I realized that a) Chrome seemed to be much faster (so first thought "Safari is really slow", but then observed that b) I could get Safari to be as fast as Chrome if I would "prime" the performance of the code by running it several times in a setTimeout loop for Safari.

So if this would be a "all the same" kind of thing for deciding between AOT vs interpreting of small modules, then these types of situations might be helped by a heuristic like this?

Naturally, if there is some complication though or other rationale that trumps here and makes this not feasible, then definitely not worth it.

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