WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] High response time with domUs

To: Xen-Users <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] High response time with domUs
From: Georg Fleckenstein <georg.fleckenstein@xxxxxx>
Date: Mon, 17 Dec 2007 19:55:52 +0100
Delivery-date: Mon, 17 Dec 2007 10:56:12 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20071216181452.GH20084@xxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <20071216181452.GH20084@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.9 (Windows/20071031)
Daniel Bareiro schrieb:
Hi all!

I'm testing my new DNS server mounted on a domU in my home LAN and I've
noticed a import delay in the time response for the host in my LAN
(domUs and non domUs), but the response time of external hosts is
minimum.
viper@marian:~$ ping -c5 debian
PING ws1.daninet (192.168.1.5) 56(84) bytes of data.
64 bytes from 192.168.1.5: icmp_seq=1 ttl=64 time=0.187 ms
64 bytes from 192.168.1.5: icmp_seq=2 ttl=64 time=0.146 ms
64 bytes from 192.168.1.5: icmp_seq=3 ttl=64 time=0.156 ms
64 bytes from 192.168.1.5: icmp_seq=4 ttl=64 time=0.197 ms
64 bytes from 192.168.1.5: icmp_seq=5 ttl=64 time=0.140 ms

- --- ws1.daninet ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 20014ms
                                                        ^^^^^^^

rtt min/avg/max/mdev = 0.140/0.165/0.197/0.024 ms


viper@marian:~$ ping -c5 yahoo.com
PING yahoo.com (66.94.234.13) 56(84) bytes of data.
64 bytes from w2.rc.vip.scd.yahoo.com (66.94.234.13): icmp_seq=1 ttl=52 
time=212 ms
64 bytes from w2.rc.vip.scd.yahoo.com (66.94.234.13): icmp_seq=2 ttl=51 
time=212 ms
64 bytes from w2.rc.vip.scd.yahoo.com (66.94.234.13): icmp_seq=3 ttl=50 
time=212 ms
64 bytes from w2.rc.vip.scd.yahoo.com (66.94.234.13): icmp_seq=4 ttl=51 
time=213 ms
64 bytes from w2.rc.vip.scd.yahoo.com (66.94.234.13): icmp_seq=5 ttl=50 
time=213 ms

--- yahoo.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4016ms
                                                        ^^^^^^
rtt min/avg/max/mdev = 212.161/213.056/213.980/0.872 ms

viper@marian:~$ dig debian.daninet

; <<>> DiG 9.4.2 <<>> debian.daninet
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39161
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;debian.daninet.                        IN      A

;; ANSWER SECTION:
debian.daninet.         3600    IN      CNAME   ws1.daninet.
ws1.daninet.            3600    IN      A       192.168.1.5

;; AUTHORITY SECTION:
daninet.                3600    IN      NS      ns1.daninet.

;; Query time: 3 msec
;; SERVER: 192.168.1.6#53(192.168.1.6)
;; WHEN: Mon Dec 10 19:40:17 2007
;; MSG SIZE  rcvd: 84

This behavior can be due to DNS server is mounted on a domU?

Thanks in advance.

Regards,
Daniel

Hello Daniel,

first you should ping to IP-Addresses to 192.168.1.6 and 192.168.1.5 without any name resolution.
There is ab big delay, but your responsetime seems to be lower than 0.2 ms.
it seems to be a problem with dns configuration.

Georg





_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>