On Fri, Jun 9, 2017 at 7:28 AM, Justin Kilpatrick wrote:
> On Fri, Jun 9, 2017 at 5:25 AM, Dmitry Tantsur wrote:
>> This number of "300", does it come from your testing or from other sources?
>> If the former, which driver were you using? What exactly problems have you
>> seen approaching this nu
On Fri, Jun 9, 2017 at 5:25 AM, Dmitry Tantsur wrote:
> On 06/08/2017 02:21 PM, Justin Kilpatrick wrote:
>>
>> Morning everyone,
>>
>> I've been working on a performance testing tool for TripleO hardware
>> provisioning operations off and on for about a year now and I've been
>> using it to try an
On Thu, Jun 8, 2017 at 11:10 AM, Emilien Macchi wrote:
> On Thu, Jun 8, 2017 at 2:21 PM, Justin Kilpatrick
> wrote:
> > Morning everyone,
> >
> > I've been working on a performance testing tool for TripleO hardware
> > provisioning operations off and on for about a year now and I've been
> > usi
This is great information Justin, thanks for sharing. It will prove useful
as we scale up our ironic deployments.
It seems to me that a reference configuration of ironic would be a useful
resource for many people. Some key decisions affecting scalability and
performance may at first seem arbitrary
On Fri, Jun 9, 2017 at 5:25 AM, Dmitry Tantsur wrote:
> This number of "300", does it come from your testing or from other sources?
> If the former, which driver were you using? What exactly problems have you
> seen approaching this number?
I haven't encountered this issue personally, but talking
On 06/08/2017 02:21 PM, Justin Kilpatrick wrote:
Morning everyone,
I've been working on a performance testing tool for TripleO hardware
provisioning operations off and on for about a year now and I've been
using it to try and collect more detailed data about how TripleO
performs in scale and pro
Hi Emilien,
I'll try and get a list of the Perf&Scale teams TripleO deployment
bugs and bring them to the deployment hackfest.
I look forward to participating!
- Justin
On Thu, Jun 8, 2017 at 11:10 AM, Emilien Macchi wrote:
> On Thu, Jun 8, 2017 at 2:21 PM, Justin Kilpatrick wrote:
>> Morning
On Thu, Jun 8, 2017 at 2:21 PM, Justin Kilpatrick wrote:
> Morning everyone,
>
> I've been working on a performance testing tool for TripleO hardware
> provisioning operations off and on for about a year now and I've been
> using it to try and collect more detailed data about how TripleO
> perform
Morning everyone,
I've been working on a performance testing tool for TripleO hardware
provisioning operations off and on for about a year now and I've been
using it to try and collect more detailed data about how TripleO
performs in scale and production use cases. Perhaps more importantly
YODA (Y