Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(3)

Unified Diff: src/heap/incremental-marking.cc

Issue 2364923002: [heap] New heuristics for starting of incremental marking. (Closed)
Patch Set: rebase Created 4 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: src/heap/incremental-marking.cc
diff --git a/src/heap/incremental-marking.cc b/src/heap/incremental-marking.cc
index beaef22ef1b911673d212118d08f1deb9e473f38..e57f216697af95ae881de9c8dd0630fcb3f1d6ad 100644
--- a/src/heap/incremental-marking.cc
+++ b/src/heap/incremental-marking.cc
@@ -401,22 +401,6 @@ void IncrementalMarking::ActivateIncrementalWriteBarrier() {
}
-bool IncrementalMarking::ShouldActivateEvenWithoutIdleNotification() {
-#ifndef DEBUG
- static const intptr_t kActivationThreshold = 8 * MB;
-#else
- // TODO(gc) consider setting this to some low level so that some
- // debug tests run with incremental marking and some without.
- static const intptr_t kActivationThreshold = 0;
-#endif
- // Don't switch on for very small heaps.
- return CanBeActivated() &&
- heap_->PromotedSpaceSizeOfObjects() > kActivationThreshold &&
- heap_->HeapIsFullEnoughToStartIncrementalMarking(
- heap_->old_generation_allocation_limit());
-}
-
-
bool IncrementalMarking::WasActivated() { return was_activated_; }

Powered by Google App Engine
This is Rietveld 408576698