Jobs metrics

Published

Updated

Reviewedbyfl

🧰

Background work, measured.

The jobs group of the metrics tab shows the memory the workers and crons of an environment use, and how often one was killed for lack of memory. It appears with the Jobs component.

Jobs memory

The memory the workers and crons use together. A sample holds the highest memory since the sample before, so it catches short spikes. A bar shows two values:

  • max: the highest sample of the hour or day. Compare it with the memory of the Jobs plan, drawn as a line.
  • typical peak: the median sample. Half of the samples were lower, half higher.

See overlapping jobs and out of memory.

Jobs OOM kills

Workers and crons the system ended because the jobs needed more memory than the plan has. A bar is the number of kills in that hour or day. See out of memory.

Labels and lines

The values each metric shows in one bar, for the time frame, and on the summary page, and the lines drawn across the chart:

MetricOne barTime frameSummaryLines
Web storagemax, last, min, avglast, max, min, avglastPlan sizes
Trafficsumsum, maxsum–
Static requestssumsum, max, minsum–
MySQL storagemax, last, min, avglast, max, min, avglastPlan sizes
PHP response timemax, avg / med / 99ilemax, avg / med / 99ileavgFast 150 ms, Good 350 ms, Slow 700 ms
PHP requestssumsum, max, minsum–
PHP memorymax, typical peakmax, typical peakmaxPlan sizes
PHP opcachemaxlast, maxlastNearly full 90%
OOM killssumsumsum–
Jobs memorymax, typical peakmax, typical peakmaxPlan sizes
Jobs OOM killssumsumsum–
404 errorssumsum, max, minsum–
500 errorssumsum, max, minsum–
503 errorssumsum, max, minsum–
504 errorssumsum, max, minsum–

Written by humans and AI in collaboration.

AI use & editorial processEdit on GitHub ↗