Avoid large allocations when compiling wasm |
||||||||||||||
Issue descriptionCurrently, wasm parallel compilation initialization creates upfront a WasmCompilationUnit per function. Each WCU's initialization requires 2 zones. Each zone has a 8KB minimum overhead (once an object is created there). In the Epic demo, with almost 200K functions, this overhead means a 3.2GB allocation before we even start compiling.
,
Jun 12 2017
The bug is marked as P3 or Feature. It should not be merged as M60 is in beta. Please contact the approriate milestone owner if you have questions. Owners: amineer@(Android), cmasso@(iOS), josafat@(ChromeOS), bustamante@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 12 2017
Switching to "Started" until we back-merge.
,
Jun 12 2017
,
Jun 12 2017
This bug requires manual review: M60 has already been promoted to the beta branch, so this requires manual review Please contact the milestone owner if you have questions. Owners: amineer@(Android), cmasso@(iOS), josafat@(ChromeOS), bustamante@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 12 2017
Please specify impacted OS's. Since we are already rolling out M59 Stable (at 5% currently), why is this change critical to be considered for M59 merge? Is there any specific user impact? Seems like it has been present in M58. Please explain the urgency for this change.
,
Jun 12 2017
Please see #1: chromium:723899 is blocked by this issue. A partial fix for that bug has been back-merged in 59 and 60. This issue here addresses the remaining of the problem. Should I tag the change off that other bug?
,
Jun 13 2017
As discussed over chat, this change has not been fully tested in canary yet. Since M59 stable is already out and bar is very high for merges, I'm rejecting merge for M59. Please confirm when this has been tested in canary, and we can re-review merge for M60.
,
Jun 16 2017
mtrofin@ - can you confirm if you were able to test this in Canary/Dev and how does it look there?
,
Jun 16 2017
It uncovered one more OOM problem, which I'm in the process of addressing. My plan is to tag that one with this issue ID, re-verify in canary, and get back on this thread, if that sounds reasonable? Thanks!
,
Jun 18 2017
sounds good - thanks!
,
Jun 18 2017
I'm marking this as merge-60-rejected for now (so it disappears from our review queue). Please re-request when you're ready.
,
Jun 20 2017
re comment#10, https://chromium-review.googlesource.com/c/540763/ landed (unfortunately, didn't get linked here, looks like gerrit won't do that for a second bug reference) I'll wait a day or two for this change to go through canary, validate, then re-apply the merge request label, as discussed.
,
Jun 22 2017
Validated canary windows 32 bit, all works well. Re-applying merge request - note I'm applying it for: https://chromium-review.googlesource.com/c/530193/ - and - https://chromium-review.googlesource.com/c/540763/ Please let me know if I need to attach the merge request separately
,
Jun 22 2017
This bug requires manual review: M60 has already been promoted to the beta branch, so this requires manual review Please contact the milestone owner if you have questions. Owners: amineer@(Android), cmasso@(iOS), josafat@(ChromeOS), bustamante@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 23 2017
Based on comments 14, approving merge to M60.
,
Jun 27 2017
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 27 2017
This was merged in https://chromium.googlesource.com/v8/v8/+/f9e1999ebce1cf71a273984da31e57e660e38bd5. We don't appear to have a M60 build with it at the moment, I'll chime back here once we do, to get confirmation from Epic.
,
Jun 28 2017
,
Jun 30 2017
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 30 2017
|
||||||||||||||
►
Sign in to add a comment |
||||||||||||||
Comment 1 by mtrofin@chromium.org
, Jun 12 2017Labels: Merge-Request-59 Merge-Request-60
Owner: mtrofin@chromium.org
Status: Fixed (was: Untriaged)