Português
English
The short answer: a load test simulates many visitors at once to see whether the site copes and where it gives way first. It is useful before a campaign or a launch. But a badly run test can bring the site down itself or look like an attack. Do it small, on a copy, and warn us first.
What the site needs
| What | What to do |
| What it measures | How many requests per second it handles, how fast it answers under load and what fails first (processor, memory, database). |
| Where to test | Preferably on a copy of the site, not on the real site with customers in it. |
| How much load | Start with little and go up in steps. The aim is to find the breaking point, not to jump past it. |
| What it is not | It is not an attack, but from the server it looks like one: many requests from one place. On shared hosting it can hit limits and be blocked: IP blocked by the firewall. |
| What the cache changes | A site with a page cache copes with far more than one without. Test with the cache on too: The page cache. |
Getting started
|
|
|
|
|
| Never test someone else’s site or a service that is not yours. And even on your own, a strong test on a shared account can affect other customers on the server and be blocked. If in doubt, ask first and use a small load. |
| If what you expect is a real peak (a campaign, an event), see Preparing for a traffic spike. To tell a real peak from an attack: DDoS attack or just a traffic spike. |
|
Want help planning a load test? Open a ticket with the address, the date and the load you plan to use. Open a support ticket |
RECOMMENDED PRODUCT Web hosting with cPanel Domain and SSL included, daily backups and the panel you already know. from 5.940,00 Kz/mo (3-year plan, with coupon) See plans |
- 0 Users Found This Useful
