8 Commits

Author	SHA1	Message	Date
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.	2015-02-04 00:10:44 +00:00
Justin Clark-Casey (justincc)	0c31eb0a5d	Add the missing deleted and re-added JobEngine class from the previous commit 8e1e8a0	2015-01-12 20:59:58 +00:00
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.	2015-01-12 20:56:37 +00:00
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. ... This is to achieve a clean separation of concerns - the watchdog is an inappropriate place for work management. Also adds a WorkManager.RunInThreadPool() class which feeds through to Util.FireAndForget. Also switches around the name and obj arguments to the new RunInThread() and RunJob() methods so that the callback obj comes after the callback as seen in the SDK and elsewhere	2014-11-25 23:56:32 +00:00
Justin Clark-Casey (justincc)	4b45a1b6ad	Change jobengine logging command to "debug jobengine log <int>" rather than loglevel, in common with similar commands.	2014-11-25 23:23:11 +00:00
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...	2014-11-25 23:21:38 +00:00
Justin Clark-Casey (justincc)	d3ed5de77d	Add loglevel to jobengine that can be controlled via "debug jobengine loglevel <level>". ... Defaults to 0 Level 1 currently does verbose logging about every queued and processed job.	2014-11-25 23:18:38 +00:00
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 ... Job engine is controlled via "debug jobengine start|stop|status". Can only currently be enabled and disabled dynamically at runtime. Currently only applies to code sending initial region data (objects, other avatar data) to a client.	2014-11-25 23:18:37 +00:00