166832 2017-01-08 14:13:04 -0800 Explore combinations of timeout and work count as a metric for when to end an increment of constraint solving 2017-11-21 14:14:00 -0800 1 1 1 Unclassified WebKit JavaScriptCore WebKit Nightly Build All All RESOLVED WONTFIX P2 Normal --- 166831 165909 1 fpizlo webkit-unassigned oldest_to_newest 1264853 0 fpizlo 2017-01-08 14:13:04 -0800 In steady state, after constraint solving marks something, we just yield to marking. But it seems like we could have a smarter metric, where we yield subject to timeout so long as we have at least one thing of new work but haven't yet hit some minimum quota of minimum work. For example we might have a mutator mark stack that always has one damn thing in it. It's probably more profitable to try to run one extra constraint after that, so long as we haven't been running for too long. 1374089 1 fpizlo 2017-11-21 14:14:00 -0800 I think that we should get rid of timeout instead. We should always full run constraints.