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-devel

Re: [Xen-devel] Re: network performance drop heavily in xen 4.0 release

To: yingbin wang <yingbin.wangyb@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: network performance drop heavily in xen 4.0 release
From: "Ronaldo C. A. Chaves" <xarqui@xxxxxxxxx>
Date: Sat, 24 Apr 2010 12:07:22 -0300
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 24 Apr 2010 08:08:20 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=3WGmcnGKFy6COjjdayoXC+/51SG5HcDwVugmD8lXMIw=; b=V2ohiU+6Iaa77jfk0Q23tqDlp9eI5pIM7gsRJeBLUzyVz03via1Nrvq7F9bvXUpch1 Z9eBTQVaAidY0hHrMA2G+ckEPt/5cNIRNMIQ203iCIawpqk91SfY/XJLLjx2pd200G3k T6NNI4xOWxi2YB8xiL+SndQqBmlLPc1P49cHM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=OAnv+uGPbhWP1S2lr4hBtr1IzX+N1Qti7vz/4qJhZkA2haC2o/LKGvuBRm7Db3V3TQ fu909zxf6iMNehuu/hvLO8c6/TNrkKf13pUk6OVUnb2w2+f49WDLEjAs1b6k6ouYkASz QvJDg6tscgf9g2yUhenfPwjkpVniM9ripopTc=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <s2sacd07b8d1004240759xd281646azf9f15b449fcebfdb@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <k2iacd07b8d1004150928k3b9581e2raa9eb1c034a36d65@xxxxxxxxxxxxxx> <x2kacd07b8d1004150939z742015daze69f618b8ee73b9@xxxxxxxxxxxxxx> <r2vacd07b8d1004160149l391b3776zac3d9b3e8ebc755@xxxxxxxxxxxxxx> <20100418185506.GN1878@xxxxxxxxxxx> <p2macd07b8d1004232342kdc03f28dl304df926633d3a6@xxxxxxxxxxxxxx> <z2hf4517e6d1004240720tb5ebcc56p601a2b38179b5c14@xxxxxxxxxxxxxx> <s2sacd07b8d1004240759xd281646azf9f15b449fcebfdb@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I compared the config-2.6.31-13xen with the config-2.6.31.13-high performance.


2010/4/24 yingbin wang <yingbin.wangyb@xxxxxxxxx>
which .config you compare with?

2010/4/24 Ronaldo C. A. Chaves <xarqui@xxxxxxxxx>:
> I compared the files and the difference is
>
> CONFIG_BLK_DEV_LOOP=m
> CONFIG_ATA_PIIX=m
> CONFIG_XEN_DEV_EVTCHN=y
>
> in config-2.6.31.13-high performance.
>
>
> 2010/4/24 yingbin wang <yingbin.wangyb@xxxxxxxxx>
>>
>> of course.
>> the attachment is the dom0 kernel compile config that fix the problem.
>> I don't know the exact config option which cause the problem, so I
>> don't test 2.6.18.8 with debug.you can compare it with the previous
>> config to find the differences.
>>
>> Here are my test results:
>>
>> test tool:  iperf-2.0.4
>> command:
>> root@xxxxxxxxxxx :      iperf -s
>> root@xxxxxxxxxxx :      iperf -c 10.250.6.25 -i 1 -t 100
>>
>> network performance:
>>
>> xen4.0+kernel2.6.31.13(with debug):
>> [ ID] Interval       Transfer     Bandwidth
>> [  4]  0.0- 9.5 sec    249 MBytes    219 Mbits/sec
>>
>> xen4.0+kernel2.6.31.13(without debug):
>> [ ID] Interval       Transfer     Bandwidth
>> [  4]  0.0-100.0 sec  10.7 GBytes    920 Mbits/sec
>>
>> xen3.4.2+kernel2.6.18.8(without debug):
>> [ ID] Interval       Transfer     Bandwidth
>> [  4]  0.0-15.0 sec  1.64 GBytes    941 Mbits/sec
>>
>> xen4.0+kernel2.6.18.8(without debug):
>> [ ID] Interval       Transfer     Bandwidth
>> [  4]  0.0-16.3 sec  1.79 GBytes    941 Mbits/sec
>>
>> Cheers,
>> wyb
>>
>> 2010/4/19 Pasi Kärkkäinen <pasik@xxxxxx>:
>> > On Fri, Apr 16, 2010 at 04:49:42PM +0800, yingbin wang wrote:
>> >> the problem is solved.
>> >>
>> >> we closed most of the debug config options. a miracle happened. the
>> >> performance returned to the level before.
>> >> we compared the .config of 2.6.18.8 with 2.6.31.13. the differences
>> >> are the debug options.
>> >> I think the default .config in 2.6.31.13 should close the debug
>> >> options or provide a way to turn off.
>> >>
>> >
>> > Could you please post the exact .config options you turned off to fix
>> > the problem?
>> > I can add that info to the wiki page.
>> >
>> > Also can you please post the performance numbers with 2.6.18.8 and
>> > pvops dom0 with and without debug? This would be interesting to know.
>> >
>> > Thanks!
>> >
>> > -- Pasi
>> >
>> >> thanks all
>> >>
>> >> Cheers,
>> >> wyb
>> >>
>> >> 2010/4/16 yingbin wang <yingbin.wangyb@xxxxxxxxx>:
>> >> > Hi:
>> >> >     I report a Bug !!!  We have just upgraded to
>> >> > xen4.0+kernel2.6.31.13 recently.  however , fond that the network
>> >> > performance drop heavily in dom0  (nearly Reduced by 2/3 vs
>> >> > xen3.4.2+kernel2.6.18.8 ) .
>> >> >
>> >> > our env :
>> >> > hardware :
>> >> >   Intel(R) Xeon(R) CPU           E5520  @ 2.27GHz
>> >> >   01:00.0 Ethernet controller: Broadcom Corporation NetXtreme II
>> >> > BCM5709 Gigabit Ethernet (rev 20)
>> >> >   01:00.1 Ethernet controller: Broadcom Corporation NetXtreme II
>> >> > BCM5709 Gigabit Ethernet (rev 20)
>> >> > compile env and filesystem :
>> >> >   Redhat AS 5.4
>> >> >
>> >> > xm info :
>> >> > -----------------------------------------------------------------
>> >> > host                   : r02k08015
>> >> > release                : 2.6.31.13xen
>> >> > version                : #1 SMP Tue Apr 13 20:38:51 CST 2010
>> >> > machine                : x86_64
>> >> > nr_cpus                : 16
>> >> > nr_nodes               : 2
>> >> > cores_per_socket       : 4
>> >> > threads_per_core       : 2
>> >> > cpu_mhz                : 2266
>> >> > hw_caps                :
>> >> >
>> >> > bfebfbff:28100800:00000000:00001b40:009ce3bd:00000000:00000001:00000000
>> >> > virt_caps              : hvm
>> >> > total_memory           : 24539
>> >> > free_memory            : 15596
>> >> > node_to_cpu            : node0:0,2,4,6,8,10,12,14
>> >> >                         node1:1,3,5,7,9,11,13,15
>> >> > node_to_memory         : node0:3589
>> >> >                         node1:12007
>> >> > node_to_dma32_mem      : node0:2584
>> >> >                         node1:0
>> >> > max_node_id            : 1
>> >> > xen_major              : 4
>> >> > xen_minor              : 0
>> >> > xen_extra              : .0
>> >> > xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p
>> >> > hvm-3.0-x86_32
>> >> > hvm-3.0-x86_32p hvm-3.0-x86_64
>> >> > xen_scheduler          : credit
>> >> > xen_pagesize           : 4096
>> >> > platform_params        : virt_start=0xffff800000000000
>> >> > xen_changeset          : unavailable
>> >> > xen_commandline        : dom0_mem=10240M
>> >> > cc_compiler            : gcc version 4.1.2 20080704 (Red Hat
>> >> > 4.1.2-46)
>> >> > cc_compile_by          : root
>> >> > cc_compile_domain      :
>> >> > cc_compile_date        : Tue Apr 13 23:04:16 CST 2010
>> >> > xend_config_format     : 4
>> >> >
>> >> > ---------------------------------------------------------------------------
>> >> >
>> >> >
>> >> > test tool:  iperf-2.0.4
>> >> > command:
>> >> > root@xxxxxxxxxxx :      iperf -s
>> >> > root@xxxxxxxxxxx :      iperf -c 10.250.6.25 -i 1 -t 100
>> >> >
>> >> > network performance:
>> >> >
>> >> > xen4.0+kernel2.6.31.13:
>> >> > [ ID] Interval       Transfer     Bandwidth
>> >> > [  4]  0.0- 9.5 sec    249 MBytes    219 Mbits/sec
>> >> >
>> >> > xen3.4.2+kernel2.6.18.8:
>> >> > [ ID] Interval       Transfer     Bandwidth
>> >> > [  4]  0.0-15.0 sec  1.64 GBytes    941 Mbits/sec
>> >> >
>> >> > BTW ,1 the disk IO performance also reduce from 90MB/s to 60MB/s.
>> >> >         2 the attachment is the dom0 kernel compile config.
>> >> >
>> >> > Cheers,
>> >> > wyb
>> >> >
>> >>
>> >> _______________________________________________
>> >> Xen-devel mailing list
>> >> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> >> http://lists.xensource.com/xen-devel
>> >
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
>>
>
>

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