error using Apache Bench (ab.exe) with Coral 8.4.0

[Guest bsenftner]

hello fellow Uniform Server enthusiasts,

 

My client wants to know how many concurrent connections the system I am building for them can handle.

 

So I looked up and read about using Apache Bench (ab.exe) here:

http://www.petefreitag.com/item/689.cfm

Trying this simple yahoo.com example:

ab.exe -n 100 -c 10 http://www.yahoo.com/

I am getting this error:

bind: An Address incompatible with the requested protocol was used. (730047)

Trying other domains like google makes no difference, same error.

 

Using google to see how others have resolved this, I find posts recommending the use of the "-B" (bind to address) option.

 

When I looked up the documentation for Apache Bench, the "-B" option is not listed, so it looks like we are getting an older version of ab.exe than what is on the official Apache Bench online documentation.

 

Revealing my utter ignorance in this area, the usage help from ab.exe says that -B is:

-B address Address to bind to when making outgoing connections

What address are they talking about? Is than an IP Address, a memory address, a port or what?

 

(FWIW, I'm a neural net developer creating a web service for access to my neural nets. Other than installing and using WAMP/MAMP/LAMP stacks, I know very little about them.)

 

Any examples, solutions, hints or places to learn how to get around this issue will be greatly appreciated.

 

(For reference, I've attached the help page generated by our copy of ab.exe to this post.)

ab_help.txt

[Guest bsenftner]

So, I got it working with this command line:

 

ab -n 100000 -c 250 -B 127.0.0.1 -r http://localhost/

 

Where this is saying:

-n: this test consists of 100,000 connection attempts

-c: while testing, do 250 connections simultaneously

-B: bind to ip address 127.0.0.1

-r: continue testing even if an error occurs

http://localhost/ : the URL to hit for these tests

 

I was pleased to see that my (physical) server handles the above command line fine, with 250 simultaneous connections. Bumping that higher fails, but 250 simultaneous connections is plenty good for my client's expected usage.

 

Another pleasant surprise was viewing the amount of memory used by the system not budging while I ran various tests.

[profl]

So, I got it working with this command line:

 

ab -n 100000 -c 250 -B 127.0.0.1 -r http://localhost/

 

Where this is saying:

-n: this test consists of 100,000 connection attempts

-c: while testing, do 250 connections simultaneously

-B: bind to ip address 127.0.0.1

-r: continue testing even if an error occurs

http://localhost/ : the URL to hit for these tests

 

I was pleased to see that my (physical) server handles the above command line fine, with 250 simultaneous connections. Bumping that higher fails, but 250 simultaneous connections is plenty good for my client's expected usage.

 

Another pleasant surprise was viewing the amount of memory used by the system not budging while I ran various tests.

 

I

 

I just use localhost without binding to 127.0.0.1

see http://forum.uniformserver.com/index.php?s...amp;#entry10564

 

And your results were???

-drl