[solved] Peformance Bottleneck

[Deltabee]

Just a as control

If we take out the -k and test on apache, we get the same thing.

So two issues:

1) Why doesn't LSWS use KA for our index.html
2) How do i get round this 13,000 connection limit!

[Deltabee]

Ok found the problem.

If we turn smart keep alives off, it works like this:

Server Software:        LiteSpeed
Server Hostname:        ourtestserver
Server Port:            2080

Document Path:          /index.html
Document Length:        59 bytes

Concurrency Level:      10
Time taken for tests:   2.599 seconds
Complete requests:      50000
Failed requests:        0
Write errors:           0
Keep-Alive requests:    49510
Total transferred:      16281870 bytes
HTML transferred:       2950000 bytes
Requests per second:    19235.25 [#/sec] (mean)
Time per request:       0.520 [ms] (mean)
Time per request:       0.052 [ms] (mean, across all concurrent requests)
Transfer rate:          6116.91 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:        0    0   0.0      0       1
Processing:     0    1   0.2      0       3
Waiting:        0    0   0.2      0       3
Total:          0    1   0.2      0       3
ERROR: The median and mean for the processing time are more than twice the standard
       deviation apart. These results are NOT reliable.
ERROR: The median and mean for the total time are more than twice the standard
       deviation apart. These results are NOT reliable.

Percentage of the requests served within a certain time (ms)
  50%      0
  66%      1
  75%      1
  80%      1
  90%      1
  95%      1
  98%      1
  99%      1
 100%      3 (longest request)

The only problem is on a simple php file that just calls phpinfo() it seems it still deosn't do KA's. Any ideas?

[NiteWave]

1) Why doesn't LSWS use KA for our index.html

lsws admin console->Server->Tuning->Smart Keep-Alive

probably current value is : Yes
set it to: No

and test again.

[Deltabee]

Originally Posted by NiteWave

lsws admin console->Server->Tuning->Smart Keep-Alive

probably current value is : Yes
set it to: No

and test again.

See above

The only problem now is php files not using KAs for some reason.

[Deltabee]

ok changed the content of the file, and it started using KA for php.

Any ideas on how to overcome this 13,000 tcp connection limit for content that doesn't use a KA for whatever reason?

[NiteWave]

maybe conntrack issue. when ab tests very slow, please check:
#sysctl net.ipv4.netfilter.ip_conntrack_max
#sysctl net.ipv4.netfilter.ip_conntrack_count

[Deltabee]

Ok found the issue.

While the VM had a high net.ipv4.netfilter.ip_conntrack_max value, the dom0 xenserver didn't

All the connections of the guests count against the max value of the dom0 server.

Increased the limit by putting the following into /etc/sysctl.conf:

net.ipv4.netfilter.ip_conntrack_max = 131072

All works perfectly now. Probably will re-enable smart keepalives.

Consider this issue solved. Thanks for your help, enterprise license bought.

PS with Apache was getting about 300 req/s on a php script, with litespeed i get 20851 req/s - almost 70 times the performance!