telepatch-server-performance

PowerBook5,4

cpu .............................. 7447A, altivec supported
clock ............................ 1499.999000MHz
board ............................ PowerBook5,4 MacRISC3 Power Macintosh
detected as ...................... 287 (PowerBook G4 15")
l2 cache ......................... 512K unified
generation ....................... NewWorld
kernel ........................... 7.1.3+deb14-powerpc
arch ............................. ppc

Machine - 30 minutes to 2026-09-04 17:16 UTC

load ............................. 0.02  (0.00-0.12)
cpu busy ......................... 1%  (1-5%)
memory ........................... 282M / 1.9G
swap ............................. 4.0K
disk ............................. 8.7G / 72G
battery .......................... 95%
uptime ........................... 30d 14h

Mean of 15 samples taken two minutes apart. Sensors: fan_rpm=no, temperature=no.

telepatch-bot.service

state ............................ active (running)
active for ....................... 30d 11h
restarts ......................... 0
memory ........................... 34M
last exit ........................ 0

Activity - last 6 hours, ending 16:00 UTC

commands ......................... 0, 0, 0, 0, 0, 0
pages published .................. 0, 0, 0, 0, 0, 0
indexes rebuilt .................. 0, 0, 0, 0, 0, 0
telegraph calls .................. 0, 0, 0, 0, 0, 0
telegraph errors ................. 0, 0, 0, 0, 0, 0
errors ........................... 0, <5, 86, 68, 0, 0

These numbers are counts and nothing else. No identifier of any kind reaches them: not a Telegraph token, a chat, a user, a title, a path or a category. Counts under 5 are shown as a bound rather than a number, and activity advances once an hour, so that no short window can be singled out. The counters live in memory that is destroyed when the service stops.

Published by telepatch-observer every 30 minutes from the machine it describes.