@kristina258 in the initial report it was about 16 minutes for 50000 entries, which is clearly not optimal and a non-linear increase. This has been fixed, as i understood.

I think the times that you are observing could be more or less expected and are growing linearly with the number of records. I remember from many years ago that i saw similar load times for that large databases with carrierroute. It could be also caused from changes in the core, e.g. in the memory management area. In the end kamailio will allocate many millions of memory chunks just to store this data. It will also highly depend on the performance of the database etc..

But its in the end of course @lbalaceanu call to make, how he sees the situation for the module.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.