Re: [openstack-dev] [neutron] trunk api performance and scale measurments

2016-12-10 Thread Armando M.
On 8 December 2016 at 20:55, Armando M. wrote: > > > On 5 December 2016 at 07:59, Bence Romsics > wrote: > >> Hi, >> >> I measured how the new trunk API scales with lots of subports. You can >> find the results here: >> >>

Re: [openstack-dev] [neutron] trunk api performance and scale measurments

2016-12-08 Thread Armando M.
On 5 December 2016 at 07:59, Bence Romsics wrote: > Hi, > > I measured how the new trunk API scales with lots of subports. You can > find the results here: > > https://wiki.openstack.org/wiki/Neutron_Trunk_API_Performance_and_Scaling > > Hope you find it useful. There

Re: [openstack-dev] [neutron] trunk api performance and scale measurments

2016-12-08 Thread Brian Stajkowski
No but I will now, ty! -- Brian Stajkowski Manager, Software Development ­ US m: 702.575.7890 irc: ski e: brian.stajkow...@rackspace.com On 12/8/16, 12:06 AM, "Ihar Hrachyshka" wrote: >Do you test with https://review.openstack.org/#/c/271830/ included? Would > >be nice

Re: [openstack-dev] [neutron] trunk api performance and scale measurments

2016-12-08 Thread Ihar Hrachyshka
Do you test with https://review.openstack.org/#/c/271830/ included? Would be nice to use a setup with the patch included as our new base. Brian Stajkowski wrote: Yes, this actually has to do with the policy check on any list of objects, including ports. The

Re: [openstack-dev] [neutron] trunk api performance and scale measurments

2016-12-07 Thread Brian Stajkowski
Yes, this actually has to do with the policy check on any list of objects, including ports. The patch has to do with bypassing this individual object check for get and delete as the individual attribute checks are bypassed. The mentality is, if you have a list of objects with a base action of

Re: [openstack-dev] [neutron] trunk api performance and scale measurments

2016-12-07 Thread John Davidge
On 12/6/16, 6:06 PM, "Tidwell, Ryan" wrote: > >I failed to make much mention of it in previous write-ups, but I also >encountered scale issues with listing ports after a certain threshold. I >haven’t gone back > to identify where the tipping point is, but I did notice that

Re: [openstack-dev] [neutron] trunk api performance and scale measurments

2016-12-06 Thread Tidwell, Ryan
GET on v2.0/ports to really bog down. -Ryan From: Armando M. [mailto:arma...@gmail.com] Sent: Monday, December 05, 2016 8:37 AM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [neutron] trunk api perfo

Re: [openstack-dev] [neutron] trunk api performance and scale measurments

2016-12-05 Thread Armando M.
On 5 December 2016 at 08:07, Jay Pipes wrote: > On 12/05/2016 10:59 AM, Bence Romsics wrote: > >> Hi, >> >> I measured how the new trunk API scales with lots of subports. You can >> find the results here: >> >>

Re: [openstack-dev] [neutron] trunk api performance and scale measurments

2016-12-05 Thread Jay Pipes
On 12/05/2016 10:59 AM, Bence Romsics wrote: Hi, I measured how the new trunk API scales with lots of subports. You can find the results here: https://wiki.openstack.org/wiki/Neutron_Trunk_API_Performance_and_Scaling Hope you find it useful. There are several open ends, let me know if you're

[openstack-dev] [neutron] trunk api performance and scale measurments

2016-12-05 Thread Bence Romsics
Hi, I measured how the new trunk API scales with lots of subports. You can find the results here: https://wiki.openstack.org/wiki/Neutron_Trunk_API_Performance_and_Scaling Hope you find it useful. There are several open ends, let me know if you're interested in following up some of them.