Hello Grant,

they use a different internal structure (in case of the carrierroute/drouting a tree structure). In case of large route sets (like more than 10.000 up to a million entries).

But depending on your scenario (and the other queries that you already do in the cfg) you maybe also might consider to query directly the database for the routing information.

Cheers,

Henning

Hi Henning,

Thanks for your reply.

I figured the memory consumption and load times would increase as the tables grow. 

Are the carrierroute and drouting modules more efficient when it comes down to memory consumption and load times? 

Regards,

Grant

On Mon, 9 Sep 2019 at 21:46, Henning Westerholt <hw@skalatan.de> wrote:

Hello Grant,

regarding the database you should be able to increase the lcr_id column
in your installation.

You might run into some limitations of the module if you increase the it
too much, for example the module supports out of the box only 128
gateways. This can be increased with a config parameter.

Keep in mind that the lcr module will loop e.g. for a DB reload over all
lcr_id values. So in case you need to have large values or large gaps
between the individual values you might want to look into another solution.

Cheers,

Henning

Am 09.09.19 um 21:10 schrieb Grant Bagdasarian:
> Hello,
>
> The database tables definition for 5.2.x mentions the lcr_id parameter
> being of unsigned short type, while in the code I only see definitions
> of type int.
>
> Is it safe to assume the parameter is of type int, so the database
> column can also be set to an integer type?
>
> Regards,
>
> Grant
>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services

-- 
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services