...turns out to be a secondary problem (but must be fixed non the less). Since the planning-job no longer drops the token now, the workers have to wait; since they are waiting actively and contending on the token, a significant slowdown can happen. Sometimes the planning job gets behind its own scheduler and thus enters dispatch, in which case it drops the GoomingToken, causing an Assertion failure on return. The **actual problem** however is the slowdown due to active spinning |
||
|---|---|---|
| .. | ||
| draw | ||
| DIR_INFO | ||
| empty.html | ||
| InterfaceConcept_Varga.mm | ||
| renderengine.html | ||
| thinkPad.ichthyo.mm | ||
| uml | ||
| workflow.mm | ||