[PATCH v5] mempool: test performance with larger bursts
Thomas Monjalon
thomas at monjalon.net
Wed Feb 21 11:22:37 CET 2024
20/02/2024 14:49, Morten Brørup:
> From: Thomas Monjalon [mailto:thomas at monjalon.net]
> > 24/01/2024 12:21, Morten Brørup:
> > > REGISTER_PERF_TEST(mempool_perf_autotest, test_mempool_perf);
> > > +REGISTER_PERF_TEST(mempool_perf_autotest_1core,
> > test_mempool_perf_1core);
> > > +REGISTER_PERF_TEST(mempool_perf_autotest_2cores,
> > test_mempool_perf_2cores);
> >
> > How do we make sure the test is skipped if we have only 1 core?
>
> Good point. Will fix in next version.
>
> >
> > > +REGISTER_PERF_TEST(mempool_perf_autotest_allcores,
> > test_mempool_perf_allcores);
> >
> > How the test duration is changed after this patch?
>
> On my test machine, the expanded test parameter set increased the duration of one test run from 20 minutes to 100 minutes.
> Before the patch, all three test runs were always executed, i.e. a total duration of 60 minutes.
>
> In other words:
> The expanded test parameter set increased the test run duration by factor five.
> Introducing the ability to optionally only test with a specific number of lcores reduced the total test duration to a third.
That's a very long test.
It would be interesting to find a way to make it shorter.
More information about the dev
mailing list