AuroraMiddleware/v8
1
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity

Let marking speed depend on the actual incremental write barrier count.

Browse Source 
Review URL: https://chromiumcodereview.appspot.com/11441011

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@13152 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
This commit is contained in:
verwaest@chromium.org 2012-12-06 15:51:42 +00:00
parent 276c790c61
commit 064bb33fdd
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/incremental-marking.cc
View File

@ -881,7 +881,7 @@ void IncrementalMarking::Step(intptr_t allocated_bytes,
// 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;