process

Base definition of a process controller

Vars
cpu_defer_count	How many times in the current run has the process deferred work till the next tick?
current_usage	Records the total usage of the current run, each 100 = 1 byond tick
disabled	TRUE if process is disabled
hang_alert_time	After this much time, the server will send an admin debug message saying the process may be hung.
hang_restart_time	After this much time, the server will automatically kill and restart the process.
hang_warning_time	This is the time after which the server will begin to show "maybe hung" in the context window.
hung	TRUE if process is blocked up
idle	TRUE if the process is not running or queued
killed	TRUE if process was killed
last_object	Settable last object this loop was processing
last_slept	Records the time (1/10s timeofday) at which the process last finished sleeping
last_task	Settable last task this loop was working on
last_usage	Records the total usage of the last run, each 100 = 1 byond tick
name	Process name
previousStatus	Previous status text
queued	TRUE if process is queued
run_start	Records the time (1/10s timeofday) at which the process last began running
running	TRUE if process is running
schedule_interval	This controls how often the process would run under ideal conditions. If the process scheduler sees that the process has finished, it will wait until this amount of time has elapsed from the start of the previous run to start the process running again.
schedule_jitter	This is added to the /datum/controller/process/var/schedule_interval when checking it. By default, this adjusts the interval by either adding or subtracting anywhere in the jitter range. For example, a jitter of `2 SECONDS` for an interval of `10 SECONDS` would give times from `8 SECONDS` to `12 SECONDS`.
status	Status text to be displayed
tick_allowance	This controls what percentage a single tick (0 to 100) the process should be allowed to run before sleeping.
tick_start	Records the world.tick_usage (0 to 100) at which the process last began running drsingh - as of byond 514, world.map_cpu is also included in this via APPROX_TICK_USE
ticks	Tick count
times_killed	Records the number of times this process has been killed and restarted
total_usage	Records the total usage over the life of the process, each 100 = 1 byond tick

Var Details

var
cpu_defer_count
– /tmp

How many times in the current run has the process deferred work till the next tick?

var
current_usage
– /tmp

Records the total usage of the current run, each 100 = 1 byond tick

var
disabled
– /tmp

TRUE if process is disabled

var
hang_alert_time
– /tmp

After this much time, the server will send an admin debug message saying the process may be hung.

var
hang_restart_time
– /tmp

After this much time, the server will automatically kill and restart the process.

var
hang_warning_time
– /tmp

This is the time after which the server will begin to show "maybe hung" in the context window.

var
hung
– /tmp

TRUE if process is blocked up

var
idle
– /tmp

TRUE if the process is not running or queued

var
killed
– /tmp

TRUE if process was killed

var
last_object
– /tmp

Settable last object this loop was processing

var
last_slept
– /tmp

Records the time (1/10s timeofday) at which the process last finished sleeping

var
last_task
– /tmp

Settable last task this loop was working on

var
last_usage
– /tmp

Records the total usage of the last run, each 100 = 1 byond tick

var
name
–

Process name

var
previousStatus
– /tmp

Previous status text

var
queued
– /tmp

TRUE if process is queued

var
run_start
– /tmp

Records the time (1/10s timeofday) at which the process last began running

var
running
– /tmp

TRUE if process is running

var
schedule_interval
– /tmp

This controls how often the process would run under ideal conditions. If the process scheduler sees that the process has finished, it will wait until this amount of time has elapsed from the start of the previous run to start the process running again.

var
schedule_jitter
– /tmp

This is added to the /datum/controller/process/var/schedule_interval when checking it. By default, this adjusts the interval by either adding or subtracting anywhere in the jitter range. For example, a jitter of 2 SECONDS for an interval of 10 SECONDS would give times from 8 SECONDS to 12 SECONDS.

For more complex behavior, override [/datum/controller/processScheduler/proc/setQueuedProcessState]. Necessary for runtime jitter range change.

var
status
– /tmp

Status text to be displayed

var
tick_allowance
– /tmp

This controls what percentage a single tick (0 to 100) the process should be allowed to run before sleeping.

var
tick_start
– /tmp

Records the world.tick_usage (0 to 100) at which the process last began running drsingh - as of byond 514, world.map_cpu is also included in this via APPROX_TICK_USE

var
ticks
– /tmp

Tick count

var
times_killed
– /tmp

Records the number of times this process has been killed and restarted

var
total_usage
– /tmp

Records the total usage over the life of the process, each 100 = 1 byond tick

/datum/controller/process

Vars

Var Details

var cpu_defer_count – /tmp

var current_usage – /tmp

var disabled – /tmp

var hang_alert_time – /tmp

var hang_restart_time – /tmp

var hang_warning_time – /tmp

var hung – /tmp

var idle – /tmp

var killed – /tmp

var last_object – /tmp

var last_slept – /tmp

var last_task – /tmp

var last_usage – /tmp

var name –

var previousStatus – /tmp

var queued – /tmp

var run_start – /tmp

var running – /tmp

var schedule_interval – /tmp

var schedule_jitter – /tmp

var status – /tmp

var tick_allowance – /tmp

var tick_start – /tmp

var ticks – /tmp

var times_killed – /tmp

var total_usage – /tmp