Revision: 19290
Author: [email protected]
Date: Tue Feb 11 16:22:26 2014 UTC
Log: Mark faster when executing write barriers.
BUG=
[email protected]
Review URL: https://codereview.chromium.org/159833002
http://code.google.com/p/v8/source/detail?r=19290
Modified:
/branches/bleeding_edge/src/incremental-marking.h
=======================================
--- /branches/bleeding_edge/src/incremental-marking.h Wed May 29 11:13:59
2013 UTC
+++ /branches/bleeding_edge/src/incremental-marking.h Tue Feb 11 16:22:26
2014 UTC
@@ -100,7 +100,7 @@
// Do some marking every time this much memory has been allocated or
that many
// heavy (color-checking) write barriers have been invoked.
static const intptr_t kAllocatedThreshold = 65536;
- static const intptr_t kWriteBarriersInvokedThreshold = 65536;
+ static const intptr_t kWriteBarriersInvokedThreshold = 32768;
// Start off by marking this many times more memory than has been
allocated.
static const intptr_t kInitialMarkingSpeed = 1;
// But if we are promoting a lot of data we need to mark faster to keep
up
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
