Bug 170774
| Summary: | WebAssembly: enable and pre-allocate fast memories on iOS | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | JF Bastien <jfbastien> |
| Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | fpizlo, jfbastien, keith_miller, mark.lam, msaboff, saam |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=170773 | ||
| Bug Depends on: | 170628 | ||
| Bug Blocks: | 159775 | ||
JF Bastien
Bug #170628 adds capabilities to pre-allocate fast memories early to avoid fragmentation, but this is currently disabled because it's still possible to obtain bimodal performance numbers when stressing fast memory allocations.
Fix the underlying issues, and pre-allocate again.
Or close this as won't fix by making fragmentation at runtime a non-issue.
Also see bug #170773 which suggests giving up cached fast memories at runtime if they haven't been used in a while.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Mark Lam
We're enabling FastMemory for iOS in https://bugs.webkit.org/show_bug.cgi?id=272232.
*** This bug has been marked as a duplicate of bug 272232 ***