Script Performance Testing

A script that runs fine alone can fall apart with 20 players, lots of objects, or a long session. Performance testing is deliberately putting your script under realistic load before that load is real.

Test under realistic conditions

Performance in an empty test place is not performance in a full server. Use Studio's multi-client test (Test → Clients and Servers → start several players) to see how your script behaves with more than one person triggering it at once.

Many bugs and slowdowns only appear when multiple clients hit the same code — which is also why best practices for multi-player scripts matters.

Test at scale and over time

Push the numbers up: more players, more instances, more events firing than you expect in normal play. And let it run — a script that is fine for two minutes can leak memory over twenty. Long-session testing catches the slow problems.

If something degrades over time, managing resource usage is usually the cause.

Measure, don't eyeball

"Feels fine" is not data. Capture frame time and memory with the MicroProfiler and stats (see understanding performance metrics), and compare against the same numbers before your change. profiling your scripts shows you how to read the breakdown.

Make it repeatable

Test the same way each time so results are comparable — same player count, same actions. When you find a regression, the fixes live in reducing script lag and optimizing script efficiency.