Skip to contents

Lists the Julia processes on this machine that ctsem started or that belong to them: this R session's engine, the engines of its sampling workers, those of other R sessions, and any left running by an R session that has ended. A Julia process can outlive what it was started for – Escape leaves one finishing an uninterruptible step in the background, and a crashed R session leaves its engine running until the engine notices – so this is where to look when a machine is busier than it should be. ctJuliaKill stops them.

Usage

ctJuliaProcesses(interval = 0.5)

Arguments

interval

Seconds over which to measure CPU use, which is what the busy column reports; 0 skips the measurement.

Value

A data frame, one row per process, with columns pid; role ("this session", "worker of this session", "another R session", "orphaned" for one whose R session has ended, "JuliaConnectoR, unrecorded", or "child of <pid>"); busy and cpu_percent over interval; cpu_seconds; memory_mb; julia_threads, the Julia thread count ctsem started it with; os_threads; r_pid, the R process it serves; started; and note, which says when this session's engine is still finishing an interrupted call.

Details

ctsem records each Julia session it starts, which is how its processes are told from any other Julia. A JuliaConnectoR session it has no record of – one started by other code, or by a ctsem too old to record it – is listed too, as is a Julia process started by one of these (precompiling the engine, typically). CPU, memory, thread and parent details need the ps package; without it, only which processes exist and whose they are.

Examples

# \donttest{
ctJuliaProcesses()
# }