4 ms·
Somebody do a benchmark with the client and server thousands of miles apart. That is not the right way to load test. You're not trying to determine how many pa
by natrius 15y ago
Somebody do a benchmark with the client and server thousands of miles apart.
That is not the right way to load test. You're not trying to determine how many pages a single client can request from a server. You're trying to isolate the performance variable. To do that, you test from a machine on the same network. The resulting values are how many requests the server can handle in a given period of time, regardless of how those requests get to the server.
- maratd 15y ago> That is not the right way to load test. False. > You're not trying to determine how many pages a single client can request from a server. True. The reason you benchmark a server with a client from a thousand miles away is that you want to know what effect common Internet noise and delays will have on RAM and CPU consumption for the http daemon. Conditions on a LAN are pretty close to ideal. Your router won't drop packets and will perform fairly well. That isn't anywhere close to true on the Internet as a whole. You do not want to push an http daemon to production that works like a champ on your LAN and has a meltdown in the real world. You want to benchmark under as close to production conditions as you can. Period.