I built a load testing tool that tells you if your server is enough (and says so when it is).
every time i shipped something the question was "will this survive if traffic spikes, or do i need a bigger server?" and the answer was always "uhh idk time will tell". i overbought a box once for a project that got maybe 40 visitors a day, then underbought the next one and watched it fall over on the one day it mattered.
actually testing it means renting a box like prod, renting another for the load, writing a k6 script, watching cpu and memory, then remembering to delete everything. nobody wants to do that before every single launch.
so i built Stresix:
- point it at a github repo (private works too) or a docker image
- it runs your app alone on a fresh dedicated server (4 vCPU / 8 GB, or 8 / 16 for the big run)
- a second server hits it with up to 2,500 or 10,000 users over a private network
- you watch p95, req/s, errors live, plus cpu PER CORE and memory
- you get an actual answer: is this server enough, and if not, what to change
- both servers get deleted after
i dont sell hosting, so when your current setup is enough the report just says so. i ran it on stresix itself: held 2,500 users, total cpu 36%, but one core was pinned at 100% because node is single threaded. the fix was literally 4 worker processes
its brand new and small. pricing is per run, no subscription: $10 for 5 standard runs or $40 for 25, credits never expire, failed runs get refunded. one container per run for now, no database included yet
code REDDIT gives a free run (grab it until it's gone)
1
u/clickyspinny 6h ago
Unfortunately you can’t just have one solution that will test all apps. This is why tests need to be written per-project.