Alright, so I'm in development right now and I'd like to understand exactly how good the benchmarks are. I've just been using apache benchmark. Do they include the server sending the files?
Also, is "requests per second" literally how many users can visit the page within one second? If it's at 30 requests per second, can literally 30 people be refreshing pages every second and the server will be fine?
It seems like a lot to me. I know a lot of people get way better stats out of their servers, but I haven't done much optimization yet.
Also, will increasing your ram increase you rps linearly? I have 512mb, so if I upgrade to 1gb, would that mean I'd get about 60 rps?
How does concurrency affect your rps?
Answer
I've just been using apache benchmark. Do they include the server sending the files?
ab? Yes, I think so
Also, is "requests per second" literally how many users can visit the page within one second? If it's at 30 requests per second, can literally 30 people be refreshing pages every second and the server will be fine?
Yes, if they perform exactly the same operations your benchmark does. Which is rarely the case.
It seems like a lot to me.
Yeah, most people would think that 30 requests per second is a very low number, but most sites would get by with that.
Also, will increasing your ram increase you rps linearly? I have 512mb, so if I upgrade to 1gb, would that mean I'd get about 60 rps?
Rarely.
How does concurrency affect your rps?
Well, it goes both ways. You might have concurrency issues, typically locks. Write operations typically lock other writers (and sometimes, writers block readers, or even readers block other readers). If you have locking, concurrent users can slow others.
On the other hand, you can have scenarios such that one users is performing I/O while another one is doing CPU work; these could be parallelized and you would be using your resources more efficiently.
Most of the time, concurrency hits you, though.
No comments:
Post a Comment