Lines Matching refs:increment

68 - ni - steps the replayer to the next increment
72 - l  - list out timestamp of current increment
184 Fundamentally the replayer loads a trace and iterates through each increment, waiting the required
185 amount of time until the increment should be executed, then executing the increment. The first
186 increment in a trace does not start at 0, rather the replayer treats its time stamp as time 0 and
193 When an increment is dispatched, it completes as much work as it can before it has to be
197 corresponding Event base on its time stamp. After completing an increment, the main thread will
198 dispatch another increment and continue.
205         wait(event.time_stamp(); //waitUntil it is time to complete this increment
209             dispatchEvent() //queue up another increment
226 and worker threads. Every time an increment is dispatched, an Event object is also created.