On Fri, Apr 15, 2016 at 7:32 AM, IWAMOTO Toshihiro
wrote:
> At Mon, 11 Apr 2016 14:42:59 +0200,
> Miguel Angel Ajo Pelayo wrote:
>>
>> On Mon, Apr 11, 2016 at 11:40 AM, IWAMOTO Toshihiro
>> wrote:
>> > At Fri, 8 Apr 2016 12:21:21 +0200,
>> > Miguel
At Mon, 11 Apr 2016 14:42:59 +0200,
Miguel Angel Ajo Pelayo wrote:
>
> On Mon, Apr 11, 2016 at 11:40 AM, IWAMOTO Toshihiro
> wrote:
> > At Fri, 8 Apr 2016 12:21:21 +0200,
> > Miguel Angel Ajo Pelayo wrote:
> >>
> >> Hi, good that you're looking at this,
> >>
> >>
> >> You
On Mon, Apr 11, 2016 at 11:40 AM, IWAMOTO Toshihiro
wrote:
> At Fri, 8 Apr 2016 12:21:21 +0200,
> Miguel Angel Ajo Pelayo wrote:
>>
>> Hi, good that you're looking at this,
>>
>>
>> You could create a lot of ports with this method [1] and a bit of extra
>> bash, without the
At Fri, 8 Apr 2016 12:21:21 +0200,
Miguel Angel Ajo Pelayo wrote:
>
> Hi, good that you're looking at this,
>
>
> You could create a lot of ports with this method [1] and a bit of extra
> bash, without the extra expense of instance RAM.
>
>
> [1]
>
Hi, good that you're looking at this,
You could create a lot of ports with this method [1] and a bit of extra
bash, without the extra expense of instance RAM.
[1]
http://www.ajo.es/post/89207996034/creating-a-network-interface-to-tenant-network-in
This effort is going to be still more
At Thu, 07 Apr 2016 16:33:02 +0900,
IWAMOTO Toshihiro wrote:
>
> At Mon, 18 Jan 2016 12:12:28 +0900,
> IWAMOTO Toshihiro wrote:
> >
> > I'm sending out this mail to share the finding and discuss how to
> > improve with those interested in neutron ovs performance.
> >
> > TL;DR: The native
At Mon, 18 Jan 2016 12:12:28 +0900,
IWAMOTO Toshihiro wrote:
>
> I'm sending out this mail to share the finding and discuss how to
> improve with those interested in neutron ovs performance.
>
> TL;DR: The native of_interface code, which has been merged recently
> and isn't default, seems to
elopment Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Neutron] OVS flow modification performance
>
> At Thu, 21 Jan 2016 02:59:16 +,
> Wuhongning wrote:
> >
> > I don't think 400 flows can show the difference , do you have setup any
> > tunne
List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] OVS flow modification performance
At Thu, 21 Jan 2016 02:59:16 +,
Wuhongning wrote:
>
> I don't think 400 flows can show the difference , do you have setup any
> tunnel peer?
>
> In fact we may set the network
pment Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Neutron] OVS flow modification performance
>
> At Mon, 18 Jan 2016 00:42:32 -0500,
> Kevin Benton wrote:
> >
> > Thanks for doing this. A couple of questions:
> >
> > What were your ro
ovs agent.
From: IWAMOTO Toshihiro [iwam...@valinux.co.jp]
Sent: Monday, January 18, 2016 4:37 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] OVS flow modification performance
At Mon, 18 Jan 2016 00:42:32 -0500,
Kevin Benton wrote:
At Mon, 18 Jan 2016 00:42:32 -0500,
Kevin Benton wrote:
>
> Thanks for doing this. A couple of questions:
>
> What were your rootwrap settings when running these tests? Did you just
> have it calling sudo directly?
I used devstack's default, which runs root_helper_daemon.
> Also, you mention
Thanks for doing this. A couple of questions:
What were your rootwrap settings when running these tests? Did you just
have it calling sudo directly?
Also, you mention that this is only ~10% of the time spent during flow
reconfiguration. What other areas are eating up so much time?
Cheers,
Kevin
I'm sending out this mail to share the finding and discuss how to
improve with those interested in neutron ovs performance.
TL;DR: The native of_interface code, which has been merged recently
and isn't default, seems to consume less CPU time but gives a mixed
result. I'm looking into this for
14 matches
Mail list logo