./httperf --server 192.168.1.1 --port 80 --uri=/index.html --num-conns 1000000 --rate 15000 --timeout 0.1
httperf --timeout=0.1 --client=0/1 --server=192.168.1.1 --port=80 --uri=/index.html --rate=15000 --send-buffer=4096 --recv-buffer=16384 --num-conns=1000000 --num-calls=1
Maximum connect burst length: 30

Total: connections 1000000 requests 1000000 replies 1000000 test-duration 66.760 s

Connection rate: 14979.0 conn/s (0.1 ms/conn, <=269 concurrent connections)
Connection time [ms]: min 0.5 avg 3.1 max 17.8 median 2.5 stddev 1.9
Connection time [ms]: connect 0.4
Connection length [replies/conn]: 1.000

Request rate: 14979.0 req/s (0.1 ms/req)
Request size [B]: 75.0

Reply rate [replies/s]: min 14972.3 avg 14979.1 max 14987.6 stddev 4.9 (13 samples)
Reply time [ms]: response 2.7 transfer 0.0
Reply size [B]: header 209.0 content 4.0 footer 0.0 (total 213.0)
Reply status: 1xx=0 2xx=1000000 3xx=0 4xx=0 5xx=0

CPU time [s]: user 14.09 system 51.83 (user 21.1% system 77.6% total 98.7%)
Net I/O: 4212.8 KB/s (34.5*10^6 bps)

Errors: total 0 client-timo 0 socket-timo 0 connrefused 0 connreset 0
Errors: fd-unavail 0 addrunavail 0 ftab-full 0 other 0

       --cpuunits num
           CPU weight for a VE. Argument is positive non-zero number, which passed to and used in kernel fair scheduler.
           The  larger  the  number  is, the more CPU time this VE get. Maximum value is 500000, minimal is 8. Number is
           relative to weights of all the other running VEs. If cpuunits not specified default value 1000 ia used.

           You can set CPU weight for VE0 (hardware node itself) as well (use vzctl  set  0  --cpuunits  num).  Usually,
           OpenVZ initscript (/etc/init.d/vz) takes care of setting this.