Reland "heap: Force incremental marking in C++ only workloads"
This is a reland of 4fde3328 Two issues in Blink tests have been fixed before this reland. Original change's description: > heap: Force incremental marking in C++ only workloads > > ... when above a certain minimum threshold. This is to guard against > memory running away in scenarios where the JS heap is empty and > there's only high throughput C++ allocations that don't allow for a > memory reducer GC to kick in. > > This logic should be revisited after Oilpan's young generation > collector is implemented which may allow switching to a more efficient > shrinking strategy for initial heap setup. > > Bug: chromium:1029379, chromium:1300028, chromium:1300492 > Change-Id: I93924fc2fe77d6226c29358d3afb1cc9d6fbf3b1 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3484319 > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> > Commit-Queue: Michael Lippautz <mlippautz@chromium.org> > Cr-Commit-Position: refs/heads/main@{#79255} Bug: chromium:1029379, chromium:1300028, chromium:1300492 Change-Id: I6cd4a4d358bc1a78f2f001ed50dd9bb3f376f49e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3488370Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#79274}
Showing
Please
register
or
sign in
to comment