Platform  /  Tz0 Performance

Module · performance

Tz0 Performance

Workstation performance and health

A slow machine has a cause. And it shows up before it turns into a ticket.

Continuous measurement · the chart exists before the ticket

Isometric illustration: a server with charts connected to workstations and laptops, each one carrying a check shield

The whole estate

Every machine reports. The server makes sense of the whole.

The agent on each machine sends CPU, memory and disk to the Tz0 server, which reads the estate as a whole — on the company network, working from home or on the road. You stop looking machine by machine and start seeing where the bottleneck is, before anyone raises a ticket.

tz0.suaempresa.local/performance/status
Estate performance index in the Tz0 console: 39.37%, with CPU, memory and disk distribution per machine
Tz0 Performance · web console

Console capture from an estate in production. Machine identification replaced; figures untouched.

What it measures

Three resources, one question: can this machine cope?

Tz0 Performance tracks CPU, memory and disk on every machine over time — not at the moment somebody complains. It shows the whole estate on one yardstick, drills down to a specific machine and tells you what to do about it: replace the disk, add memory, or retire what is sitting idle.

CPU, memory and disk over time

The agent records the use of each resource hour by hour. The screen shows the curve of the week, not a one-second spike — that is the difference between “it is slow right now” and “it lives at its limit”.

The estate on a single scale

Every machine gets a grade — from “very good” to “critical” — for CPU, for memory and for disk. You can see from across the room which machines are struggling, and at what.

Recommended action

Where there is too much headroom, the module suggests a downgrade; where space is short, a disk upgrade. Replacing hardware stops being a hunch and gets a measured reason.

How it works

From the reading to the replacement call.

Measurement is continuous and incremental: by the time the ticket arrives, that machine’s curve is already on the server.

01 Measure Tracks CPU, memory, disk on the machine, nonstop. 02 Send Only the difference travels the local network. 03 Consolidate The server puts the estate on one scale. 04 Point Shows what is at the limit and since when. 05 Decide Replace, upgrade or retire. The slow machine nobody filed a ticket for shows up all the same — the chart does not wait for the complaint.

Console

From the estate down to the machine, all in the browser.

Device status screen in Tz0 Performance, with an overall estate index of 39.37% and the CPU, memory and disk distribution across 29 machines
The whole estate on one scale. Overall index at 39.37%, and the CPU, memory and disk distribution across 29 machines — from “very good” to “critical”. Below, every device with its three coloured bars: you can see from across the room which one is struggling, and at what.
Single machine performance screen in Tz0, with average CPU, memory and disk usage and the hour-by-hour curve across the week
One machine, hour by hour. From the estate you drill down to a single computer: CPU at 45.21% (normal), memory at 38.20% (normal), disk C at 97.79% — extreme. The curve covers the whole week, not a snapshot. The full disk shows up before it locks the machine.
Recommendations screen in Tz0 Performance, with per-device disk downgrade or upgrade suggestions
And what to do about the number. The module does not stop at the chart: it recommends. A machine with room to spare gets a downgrade suggestion; a tight disk, an upgrade — each with its clock speed and free space alongside. Measuring turns into a purchasing decision instead of a hunch.

Screens from a real estate in production, not a demo environment. Machine identification was replaced with a generic equivalent before publishing; percentages, clock speeds, capacity and the interface itself are untouched.

Find out which machine on your estate is at its limit.