0

Is there a way to know how many requests WAMP can handle in a second. And is there a way to increase that?

By WAMP i mean the package software installed on the local machines

3
  • 1, 100, 100000, pick one
    – Dagon
    Feb 27, 2012 at 8:53
  • run ab against it and find out!
    – tylerl
    Feb 27, 2012 at 9:48
  • 3
    How many horsepowers does a car have? ;) Totally useless question, because it depends on programmer stupidity, application specifics and server power.
    – TomTom
    Feb 27, 2012 at 9:49

3 Answers 3

2

As Amber said, it depends on the specs of the server. However, you can do benchmarks with ab.exe, located in the apache\bin directory.

More info on Apache Bench: http://www.petefreitag.com/item/689.cfm

2

It all depends on your server specs, what other processes are running, how intensive your request handling is, et cetera.

In other words, there's no specific answer to your question. For tips on tuning performance, you might want to ask on ServerFault.

2
  • By WAMP i mean the package software installed on the local machines.
    – user963631
    Feb 27, 2012 at 8:57
  • Still irrelevant. Some applications that you write use more resources than others. How many kg load can I put on a vehicle? Some 100kg, some 40 tons. Depends on the vehicle. And putting 100 liters water into acars is hard when it is not in bottles ;) It is easier in a tank. WAMP is a tachnology stack. Some site are slim, some require a lot of database IO or processing.
    – TomTom
    Feb 27, 2012 at 9:51
0

I have heard figures ranging from about 10-50 for an unoptimized webapp, > 100 && < 500 for an optimized webapp with database optimizations, and 1000+ for a webapp behind a load balancer, some caching, and 10000+ with proper horizontal and vertical scaling and tinkering with your framework/language to squeeze every last bit of performance out of it.

These are just estimates off the top of my head (and probably wrong, but that's the point of guestimation). They will differ based on what you're serving, whether you've configured your stack to squeeze performance, whether you've optimized your code, the limitations of your hardware and bandwidth at this point and whatever else life has to throw at you.

Not the answer you're looking for? Browse other questions tagged .