Re: apache22 is very slow on NetBSD 6.0_STABLE

To: Greg Troxel <gdt%ir.bbn.com@localhost>
Subject: Re: apache22 is very slow on NetBSD 6.0_STABLE
From: Pongthep Kulkrisada <ptkrisada%gmail.com@localhost>
Date: Sun, 3 Feb 2013 13:02:07 +0700

Thank you for your kind response.

* Greg Troxel (gdt%ir.bbn.com@localhost) wrote:
>> It takes very long time to load the page (10+ seconds).
> Check that dns works.  You should be able to 'dig -x a.b.c.d' on the
> apache host, using the address of the request host, and it should be
> very fast, less than 100ms the first time, more or less, and even faster
> on subsequent times.
It is definitely fast (even the 1st dig).
This is the output of the 2nd dig.

; <<>> DiG 9.9.2-P1 <<>> -x 192.168.1.11
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 38174
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4000
;; QUESTION SECTION:
;11.1.168.192.in-addr.arpa.     IN      PTR

;; Query time: 90 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Sun Feb  3 10:15:25 2013
;; MSG SIZE  rcvd: 54

> Then, if that's ok, run tcpdump and watch the connetion.  Use -s1500 -X.
I ran it for shorter than one minute.
I can say that around one thousand transactions were monitored.
This includes udp, icmp and many unrelated IP addresses.
At the test I turned on only 2 machines and both are 192.168.1.x.
During the test I only fire up firefox on the client.
And monitor with tcpdump on NetBSD server.
And nothing else, I did not do ping or whatever.
I believe that these udp and icmp are for some background daemons.
And I believe that these addresses are for dns purpose, which I don't know.
In my small network, I only refer each machine by addressing 192.168.1.x.

Trimmed output for tcpdump follows.

10:16:01.282632 IP 123.140.180.31 > 192.168.1.11: ICMP 123.140.180.31 udp port 
54246 unreachable, length 139
10:16:01.453150 IP 91.189.218.81 > 192.168.1.11: ICMP 91.189.218.81 udp port 
52213 unreachable, length 139
10:16:01.739852 IP 101.99.5.220.53536 > 192.168.1.11.60483: UDP, length 103
10:16:01.739976 IP 192.168.1.11.60483 > 101.99.5.220.53536: UDP, length 277
...
10:16:02.138698 IP 192.168.1.11.60483 > 59.124.221.187.22039: UDP, length 103
10:16:02.138726 IP 192.168.1.11.60483 > 173.59.60.70.49106: UDP, length 103
...
10:16:03.618894 IP6 fe80::d71:50ac:1282:d1fc.63207 > ff02::c.ssdp: UDP, length 
146
        0x0090:  3a20 5634 3a49 5056 363a 4c69 6e6b 4c6f  :.V4:IPV6:LinkLo
...
10:16:48.153695 IP 192.168.1.11.60483 > 89.29.221.74.36508: UDP, length 103
10:16:48.153798 IP 192.168.1.11.60483 > 217.12.72.248.21855: UDP, length 103
...
10:16:48.931870 IP 192.168.1.11.49467 > 192.168.1.100.http: Flags [S], seq 
4097870430, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
10:16:48.932744 IP 192.168.1.100.http > 192.168.1.11.49467: Flags [S.], seq 
3009077226, ack 4097870431, win 32768, options [mss 1460,nop,wscale 
3,sackOK,nop,nop], length 0
10:16:48.932777 IP 192.168.1.11.49467 > 192.168.1.100.http: Flags [.], ack 1, 
win 16425, length 0
10:16:48.936157 IP 192.168.1.11.49467 > 192.168.1.100.http: Flags [P.], seq 
1:289, ack 1, win 16425, length 288
10:16:49.128295 IP 192.168.1.11.60483 > 184.10.241.86.14813: UDP, length 103
10:16:49.128300 IP 192.168.1.11.60483 > 151.51.36.110.29194: UDP, length 103
10:16:49.128301 IP 192.168.1.11.60483 > 142.166.53.221.21937: UDP, length 103
10:16:49.130699 IP 192.168.1.100.http > 192.168.1.11.49467: Flags [.], ack 289, 
win 4197, length 0
10:16:49.310382 IP 192.168.1.100.http > 192.168.1.11.49467: Flags [P.], seq 
1:334, ack 289, win 4197, length 333
10:16:49.310642 IP 192.168.1.100.http > 192.168.1.11.49467: Flags [.], seq 
334:1794, ack 289, win 4197, length 1460
10:16:49.310688 IP 192.168.1.11.49467 > 192.168.1.100.http: Flags [.], ack 
1794, win 15976, length 0
10:16:49.310847 IP 192.168.1.100.http > 192.168.1.11.49467: Flags [P.], seq 
1794:2649, ack 289, win 4197, length 855
10:16:49.311680 IP 192.168.1.11.49467 > 192.168.1.100.http: Flags [.], ack 
2649, win 16211, length 0
10:16:49.406215 IP 192.168.1.100.http > 192.168.1.11.49467: Flags [F.], seq 
2649, ack 289, win 4197, length 0
10:16:49.406274 IP 192.168.1.11.49467 > 192.168.1.100.http: Flags [.], ack 
2650, win 16211, length 0
10:16:49.406629 IP 192.168.1.11.49467 > 192.168.1.100.http: Flags [F.], seq 
289, ack 2650, win 16211, length 0
10:16:49.406770 IP 192.168.1.100.http > 192.168.1.11.49467: Flags [.], ack 290, 
win 4197, length 0
10:16:49.485373 IP 192.168.1.11.49468 > 192.168.1.100.http: Flags [S], seq 
3441610158, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
10:16:49.485606 IP 192.168.1.100.http > 192.168.1.11.49468: Flags [S.], seq 
3039208026, ack 3441610159, win 32768, options [mss 1460,nop,wscale 
3,sackOK,nop,nop], length 0
10:16:49.485614 IP 192.168.1.11.49468 > 192.168.1.100.http: Flags [.], ack 1, 
win 16425, length 0
10:16:49.485882 IP 192.168.1.11.49469 > 108.59.8.214.http: Flags [S], seq 
3589154845, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
10:16:49.487335 IP 192.168.1.11.49468 > 192.168.1.100.http: Flags [P.], seq 
1:300, ack 1, win 16425, length 299
10:16:49.488031 IP 192.168.1.11.49450 > 180.180.251.90.http: Flags [P.], seq 
664:1039, ack 2555, win 16458, length 375
10:16:49.591518 IP 180.180.251.90.http > 192.168.1.11.49450: Flags [P.], seq 
2555:2794, ack 1039, win 8908, length 239
10:16:49.618666 IP6 fe80::d71:50ac:1282:d1fc.63207 > ff02::c.ssdp: UDP, length 
146
        0x0090:  3a20 5634 3a49 5056 363a 4c69 6e6b 4c6f  :.V4:IPV6:LinkLo
10:16:49.637493 IP 192.168.1.100.http > 192.168.1.11.49468: Flags [P.], seq 
1:461, ack 300, win 4197, length 460
10:16:49.726040 IP 192.168.1.11.49470 > 108.59.8.214.http: Flags [S], seq 
733618145, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
10:16:49.771350 IP 192.168.1.11.49450 > 180.180.251.90.http: Flags [P.], seq 
1039:1393, ack 2794, win 16399, length 354
10:16:49.843128 IP 192.168.1.11.49468 > 192.168.1.100.http: Flags [.], ack 461, 
win 16310, length 0
10:16:49.875973 IP 180.180.251.90.http > 192.168.1.11.49450: Flags [P.], seq 
2794:3031, ack 1393, win 9444, length 237
10:16:49.876848 IP 192.168.1.11.49460 > 23.23.74.52.http: Flags [P.], seq 
666:1300, ack 253, win 16622, length 634
10:16:49.877206 IP 192.168.1.11.49460 > 23.23.74.52.http: Flags [P.], seq 
1300:1329, ack 253, win 16622, length 29
10:16:49.890628 IP 192.168.1.11.49471 > 108.59.8.227.http: Flags [S], seq 
1816520286, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
10:16:49.893942 IP 192.168.1.11.49472 > 108.59.8.227.http: Flags [S], seq 
2648865603, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
10:16:50.075597 IP 192.168.1.11.49450 > 180.180.251.90.http: Flags [.], ack 
3031, win 16339, length 0
10:16:50.128219 IP 192.168.1.11.60483 > 78.72.57.214.37720: UDP, length 103
10:16:50.128224 IP 192.168.1.11.60483 > 217.122.216.84.14682: UDP, length 103
10:16:50.128226 IP 192.168.1.11.60483 > 24.71.140.185.23127: UDP, length 103
10:16:50.128227 IP 192.168.1.11.60483 > 81.250.217.27.53907: UDP, length 103
10:16:50.136259 IP 192.168.1.11.49473 > 108.59.8.227.http: Flags [S], seq 
2071757241, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
10:16:50.136389 IP 192.168.1.11.49474 > 108.59.8.227.http: Flags [S], seq 
3760543831, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
10:16:50.137975 IP 192.168.1.11.49475 > 74.125.128.95.http: Flags [S], seq 
3348149308, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
10:16:50.138770 IP 192.168.1.11.49476 > 108.59.8.227.http: Flags [S], seq 
3386485104, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
10:16:50.250396 IP 23.23.74.52.http > 192.168.1.11.49460: Flags [.], ack 1329, 
win 68, length 0
10:16:50.253131 IP 23.23.74.52.http > 192.168.1.11.49460: Flags [P.], seq 
253:579, ack 1329, win 68, length 326
10:16:50.353885 IP 192.168.1.11.61433 > 192.168.1.1.domain: 65051+ A? 
ajax.googleapis.com. (37)
10:16:50.354338 IP 192.168.1.1.domain > 192.168.1.11.61433: 65051 2/0/0 CNAME 
googleapis.l.google.com., A 74.125.128.95 (87)
10:16:50.355124 IP 192.168.1.11.49477 > 74.125.128.95.http: Flags [S], seq 
2369723903, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
10:16:50.355943 IP 192.168.1.11.49478 > 108.59.13.4.http: Flags [S], seq 
1934109084, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
10:16:50.453265 IP 192.168.1.11.49460 > 23.23.74.52.http: Flags [.], ack 579, 
win 16540, length 0
10:16:51.128386 IP 192.168.1.11.60483 > 62.34.223.217.21697: UDP, length 103
10:16:52.485694 IP 192.168.1.11.49469 > 108.59.8.214.http: Flags [S], seq 
3589154845, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
10:16:52.723216 IP 192.168.1.11.49470 > 108.59.8.214.http: Flags [S], seq 
733618145, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
10:16:52.895749 IP 192.168.1.11.49471 > 108.59.8.227.http: Flags [S], seq 
1816520286, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0

Thanks,
-- 
Pongthep Kulkrisada
 
"UNIX is basically a simple operating system,
but you have to be a genius to understand the simplicity."
-- Dennis M. Ritchie

Follow-Ups:
- Re: apache22 is very slow on NetBSD 6.0_STABLE
  - From: matthew sporleder
- Re: apache22 is very slow on NetBSD 6.0_STABLE
  - From: Greg Troxel

References:
- apache22 is very slow on NetBSD 6.0_STABLE
  - From: Pongthep Kulkrisada
- Re: apache22 is very slow on NetBSD 6.0_STABLE
  - From: Greg Troxel

Prev by Date: Workaround for PR 47241 (bad conditional expression errors during build)
Next by Date: Re: time command sometimes shows garbage in "user" and "sys"
Previous by Thread: Re: apache22 is very slow on NetBSD 6.0_STABLE
Next by Thread: Re: apache22 is very slow on NetBSD 6.0_STABLE
Indexes:

Home | Main Index | Thread Index | Old Index