Bug 166832

Summary: Explore combinations of timeout and work count as a metric for when to end an increment of constraint solving
Product: WebKit Reporter: Filip Pizlo <fpizlo>
Component: JavaScriptCoreAssignee: Nobody <webkit-unassigned>
Severity: Normal    
Priority: P2    
Version: WebKit Nightly Build   
Hardware: All   
OS: All   
Bug Depends on: 166831    
Bug Blocks: 165909    

Description Filip Pizlo 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.
Comment 1 Filip Pizlo 2017-11-21 14:14:00 PST
I think that we should get rid of timeout instead.  We should always full run constraints.