[dpdk-dev] [PATCH] app/test: reduced duration of red_autotest

2016-06-08 Thread Thomas Monjalon
2016-06-08 15:56, Kantecki, Tomasz: > Hi Thomas, > > > > 12s is long for a functional test. We are used to have tests of less than > > > 1s. > > > Do you think this magnitude order can be achieved for red tests? > > > > This is a real challenge :) Let me take another look into it. > > I had a

[dpdk-dev] [PATCH] app/test: reduced duration of red_autotest

2016-06-08 Thread Kantecki, Tomasz
Hi Thomas, > > 12s is long for a functional test. We are used to have tests of less than > > 1s. > > Do you think this magnitude order can be achieved for red tests? > > This is a real challenge :) Let me take another look into it. I had a 2nd look into this test suite and reducing time for fun

[dpdk-dev] [PATCH] app/test: reduced duration of red_autotest

2016-06-07 Thread Thomas Monjalon
Hi Tomasz, Thanks for splitting tests. 2016-06-07 14:49, Tomasz Kantecki: > 'red_autotest' changed to run only functional tests without test #4 which was > taking ~53 seconds. 'red_autotest' takes ~12[s] now. 12s is long for a functional test. We are used to have tests of less than 1s. Do you th

[dpdk-dev] [PATCH] app/test: reduced duration of red_autotest

2016-06-07 Thread Kantecki, Tomasz
Hi Thomas, > 12s is long for a functional test. We are used to have tests of less than 1s. > Do you think this magnitude order can be achieved for red tests? This is a real challenge :) Let me take another look into it. Regards, Tomasz

[dpdk-dev] [PATCH] app/test: reduced duration of red_autotest

2016-06-07 Thread Tomasz Kantecki
'red_autotest' changed to run only functional tests without test #4 which was taking ~53 seconds. 'red_autotest' takes ~12[s] now. 'red_perf' has been added to run performance tests only (~26[s]). 'red_all' has been added to run all functional tests (including #4) and perfromance tests. This reflec