Hi Venu, On Wed, Nov 13, 2019 at 10:42:07AM +0530, Venumadhav Josyula wrote: > Hi, > > Few more points > > Operating system : Centos 7.6 > Logging mechanism : syslog > > We have logged using syslog before the call and syslog after the call. > > Thanks & Regards > Venu > > On Wed, 13 Nov 2019 at 10:37, Venumadhav Josyula <vjosy...@gmail.com> wrote: > > > Hi , > > We are using 'rte_mempool_create' for allocation of flow memory. This has > > been there for a while. We just migrated to dpdk-18.11 from dpdk-17.05. Now > > here is problem statement > > > > Problem statement : > > In new dpdk ( 18.11 ), the 'rte_mempool_create' take approximately ~4.4 > > sec for allocation compared to older dpdk (17.05). We have som 8-9 mempools > > for our entire product. We do upfront allocation for all of them ( i.e. > > when dpdk application is coming up). Our application is run to completion > > model. > > > > Questions:- > > i) is that acceptable / has anybody seen such a thing ? > > ii) What has changed between two dpdk versions ( 18.11 v/s 17.05 ) from > > memory perspective ?
Could you give some more details about you use case? (hugepage size, number of objects, object size, additional mempool flags, ...) Did you manage to reproduce it in a small test example? We could do some profiling to investigate. Thanks for the feedback. Olivier
