Revision: 13152
Author: [email protected]
Date: Thu Dec 6 07:51:42 2012
Log: Let marking speed depend on the actual incremental write barrier
count.
Review URL: https://chromiumcodereview.appspot.com/11441011
http://code.google.com/p/v8/source/detail?r=13152
Modified:
/branches/bleeding_edge/src/incremental-marking.cc
=======================================
--- /branches/bleeding_edge/src/incremental-marking.cc Fri Nov 30 01:42:20
2012
+++ /branches/bleeding_edge/src/incremental-marking.cc Thu Dec 6 07:51:42
2012
@@ -881,7 +881,7 @@
// allocation), so to reduce the lumpiness we don't use the write
barriers
// invoked since last step directly to determine the amount of work to
do.
intptr_t bytes_to_process =
- marking_speed_ * Max(allocated_, kWriteBarriersInvokedThreshold);
+ marking_speed_ * Max(allocated_,
write_barriers_invoked_since_last_step_);
allocated_ = 0;
write_barriers_invoked_since_last_step_ = 0;
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
