Commit History

Author SHA1 Message Date
  Melanie Thielker b16abc8166 Massive tab and trailing space cleanup 7 years ago
  UbitUmarov 59f6353ac1 close a resource on jobengine.close() 7 years ago
  UbitUmarov baf8e762a6 change JobEngine stop code and add a extra check for thread removed on watchdog timeout checks 8 years ago
  Melanie Thielker 774ac5e96b If no job engine is started at all, keep checking it's status from 8 years ago
  Justin Clark-Casey (justincc) 686b22da6e On shutdown (job engine stop), don't allow the ObjectDisposedException on BlockingCollection.Take() to propogate if the running thread checked IsRunning before the stop thread set it and disposed of the canellation source. 9 years ago
  Justin Clark-Casey (justincc) 6834393821 Fix bug in JobEngine where an attempt to restart after stop would trigger an exception because the cancellation source was not recreated. 9 years ago
  Justin Clark-Casey (justincc) 0c31eb0a5d Add the missing deleted and re-added JobEngine class from the previous commit 8e1e8a0 9 years ago
  Justin Clark-Casey (justincc) 8e1e8a0920 Make the performance controlling job processing threads introduced in conference code use a generic JobEngine class rather than 4 slightly different copy/pasted versions. 9 years ago
  Justin Clark-Casey (justincc) 86367d7219 refactor: Move methods to start a monitored thread, start work in its own thread and run work in the jobengine from Watchdog to a WorkManager class. 10 years ago
  Justin Clark-Casey (justincc) 4b45a1b6ad Change jobengine logging command to "debug jobengine log <int>" rather than loglevel, in common with similar commands. 10 years ago
  Justin Clark-Casey (justincc) 6c043dd6ff If an exception makes it to the top of a JobEngine request, catch and log instead of letting it terminate the simulator... 10 years ago
  Justin Clark-Casey (justincc) d3ed5de77d Add loglevel to jobengine that can be controlled via "debug jobengine loglevel <level>". 10 years ago
  Justin Clark-Casey (justincc) 859b1c5ba4 Add experimental job engine to see if queueing some existing async work during root agent entry to a region improves perf rather than always attempting to execute everything concurrently 10 years ago