Methods / L4 / SAMP
L4 · NetworkGameUDPVolumetricQuery Flood

SAMP stress test

Sends emulated San Andreas Multiplayer query and session UDP traffic to validate how a SA-MP server you operate handles a flood that mimics real clients.

Run SAMP test All methods
600k pps
peak rate

How it works

SA-MP servers answer UDP query packets and carry player sessions over UDP, and this method reproduces those exchange patterns at high volume. The traffic looks like a swarm of querying and connecting clients, so simple signature filters that whitelist game ports without inspecting state pass it through. It validates whether your query rate limiting, session validation, and the server's own packet processing budget survive sustained game-shaped load.

Parameters

pps600k ppsPacket rate aimed at the server's UDP ports
payloadSA-MP query/sessionPayloads modeled on real SA-MP client exchanges
sourcesregional spreadSpreads traffic across many source addresses
duration10-600 sLength of the test window

Run it from the CLI

retro-cli
$ retro run samp --target 203.0.113.45 --port 443 --duration 120

SAMP FAQ

Is SAMP testing legal?+
Only against infrastructure you own or are authorized to test. RETRO//STRESS requires authorized targets.
What does SAMP stress?+
Sends emulated San Andreas Multiplayer query and session UDP traffic to validate how a SA-MP server you operate handles a flood that mimics real clients.
Can I combine it with other methods?+
Yes, add it as a step in a packet chain to sequence it with other protocols.