Performance Tester

Role

Checks whether an experience runs smoothly enough for its target context.

Description

A Performance Tester measures whether an experience runs well enough, and keeps running well enough, for its target context. They profile frame rates, memory, load times, and thermal behavior, turning a vague sense of choppiness into numbers a team can act on.

In this field the word carries double weight: performance here means computation, not acting. The stakes are physical either way. A dropped frame on a monitor is an annoyance, but sustained frame drops in a headset make people ill, and a standalone device that throttles after twenty minutes fails exactly when the queue outside is longest.

Discipline-Specific Description

Performance testing pairs profiling tools with realistic conditions: full scenes, long sessions, hot devices, actual venue hardware. Budgets that hold in the editor give way in exactly these situations, which is why the role tests there.

Scope Note

Usually includes frame time and memory profiling, load and stress testing, thermal and battery endurance runs, target-device verification, regression tracking against performance budgets, and reporting that ties measurements to specific scenes and assets.

Boundary Note

The Performance Tester produces the evidence; deciding what to cut or optimize belongs to technical artists, developers, and directors. The role also differs from Device Compatibility Testing, which asks whether the experience works across hardware at all. This one asks whether it runs well enough, for long enough.

Collaboration Note

Close collaborators include optimization artists, technical artists, developers, device compatibility testers, and producers deciding what the venue hardware can honestly sustain.

Related entries