RESOLVED WONTFIX 166832
Explore combinations of timeout and work count as a metric for when to end an increment of constraint solving 
https://bugs.webkit.org/show_bug.cgi?id=166832
Summary Explore combinations of timeout and work count as a metric for when to end an...
Filip Pizlo
Reported 2017-01-08 14:13:04 PST
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.
Attachments
Add attachment proposed patch, testcase, etc.
Filip Pizlo
Comment 1 2017-11-21 14:14:00 PST
I think that we should get rid of timeout instead. We should always full run constraints.
Note You need to log in before you can comment on or make changes to this bug.