| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
a threadpool) via Watchdog.RunInThread() rather than Util.RunThreadNoTimeout()
The functionality is the same but this allow us to monitor such tasks via "show threads" and abort them for test purposes, etc.
Also extends thread names to provide more info (e.g. SendInitialDataToClient says what client the task is for).
|
|
|
|
| |
These have the format server.thread.<thread-name>
|
|
|
|
|
|
| |
not hold.
Not yet in use.
|
|
|
|
|
|
| |
delta over time.
The chief motivation for this is to be able to tell whether there's any impact on incoming packet processing from enabling extra packet pooling.
|
| |
|
|
|
|
|
|
|
| |
passing the original ThreadWatchdogInfo structure.
This is to avoid the possibility of misleading reporting if a watchdog update outraces an alarm.
Should address any remaining issues from http://opensimulator.org/mantis/view.php?id=6012
|
|
|
|
| |
This is to avoid false positives when the machine is under heavy load whilst starting up.
|
|
with other monitoring code from OpenSim.Framework
|