[PATCH] test-flow-perf: support measuring 2nd round rate

[Bing Zhao]

OK. So do you mean the parameter should be used to set the iteration times? And we will output the last time iteration results?
Do we need a global AVG result for all the iterations?

> -----Original Message-----
> From: Wisam Jaddo <wisamm at nvidia.com>
> Sent: Tuesday, November 18, 2025 8:43 PM
> To: Bing Zhao <bingz at nvidia.com>; Slava Ovsiienko
> <viacheslavo at nvidia.com>; dev at dpdk.org; Raslan Darawsheh
> <rasland at nvidia.com>
> Cc: Ori Kam <orika at nvidia.com>; Dariusz Sosnowski <dsosnowski at nvidia.com>;
> Suanming Mou <suanmingm at nvidia.com>; Matan Azrad <matan at nvidia.com>; NBU-
> Contact-Thomas Monjalon (EXTERNAL) <thomas at monjalon.net>
> Subject: RE: [PATCH] test-flow-perf: support measuring 2nd round rate
> 
> Hi,
> 
> > -----Original Message-----
> > From: Bing Zhao <bingz at nvidia.com>
> > Sent: Monday, November 17, 2025 9:30 AM
> > To: Slava Ovsiienko <viacheslavo at nvidia.com>; dev at dpdk.org; Raslan
> > Darawsheh <rasland at nvidia.com>; Wisam Jaddo <wisamm at nvidia.com>
> > Cc: Ori Kam <orika at nvidia.com>; Dariusz Sosnowski
> > <dsosnowski at nvidia.com>; Suanming Mou <suanmingm at nvidia.com>; Matan
> > Azrad <matan at nvidia.com>; NBU-Contact-Thomas Monjalon
> > (EXTERNAL) <thomas at monjalon.net>
> > Subject: [PATCH] test-flow-perf: support measuring 2nd round rate
> >
> > In some driver, the flow table may start from a small size and
> > increase based on the rules number. The table resize may not reflact
> > the actual rules insertion rate due to the extra overhead.
> >
> > Keeping 1 rule in the table and measuring the 2nd iteration would be
> > more accurate.
> 
> I'm ok with the approach of enabling the measurement of the table warm up
> effect over the insertion/deletion, but I tend to believe that we should
> have it by iterations were user can set the needed rounds instead of
> depending on only 2 rounds
> 
> BRs,
> Wisam Jaddo