Re: [PATCH v1 2/6] app/test: add allocator performance benchmark

2022-01-20 Thread Bruce Richardson
On Wed, Jan 19, 2022 at 09:12:35PM +, Dmitry Kozlyuk wrote: > > From: Bruce Richardson > > [...] > > > What is the expected running time of this test? When I tried it out > > on my > > > machine it appears to hang after the following output: > > > [...] > > It always runs within 50 seconds on

RE: [PATCH v1 2/6] app/test: add allocator performance benchmark

2022-01-19 Thread Dmitry Kozlyuk
> From: Bruce Richardson > [...] > > What is the expected running time of this test? When I tried it out > on my > > machine it appears to hang after the following output: > > [...] It always runs within 50 seconds on my machine (E5-1650 v3 @ 3.50GHz). Judging by the output, it runs faster than y

Re: [PATCH v1 2/6] app/test: add allocator performance benchmark

2022-01-17 Thread Aaron Conole
Dmitry Kozlyuk writes: > Memory allocator performance is crucial to applications that deal > with large amount of memory or allocate frequently. DPDK allocator > performance is affected by EAL options, API used and, at least, > allocation size. New autotest is intended to be run with different >

Re: [PATCH v1 2/6] app/test: add allocator performance benchmark

2022-01-17 Thread Bruce Richardson
On Mon, Jan 17, 2022 at 03:47:41PM +, Bruce Richardson wrote: > On Mon, Jan 17, 2022 at 10:07:57AM +0200, Dmitry Kozlyuk wrote: > > Memory allocator performance is crucial to applications that deal > > with large amount of memory or allocate frequently. DPDK allocator > > performance is affecte

Re: [PATCH v1 2/6] app/test: add allocator performance benchmark

2022-01-17 Thread Bruce Richardson
On Mon, Jan 17, 2022 at 10:07:57AM +0200, Dmitry Kozlyuk wrote: > Memory allocator performance is crucial to applications that deal > with large amount of memory or allocate frequently. DPDK allocator > performance is affected by EAL options, API used and, at least, > allocation size. New autotest