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(a)skalatan.de> wrote:

Am 10.09.19 um 10:08 schrieb Henning Westerholt: 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) somehow there is some content missing in the e-mail, In case of large route sets (like more than 10.000 up to a million entries) they can be queried faster as e.g. a linear list. 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 Am 10.09.19 um 09:59 schrieb Grant Bagdasarian: 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<mailto: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: -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org<mailto: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

Hello Grant, yes, traversing a linear list is of course slower as a tree structure. This is one major advantage of using this modules. As the modules query a in-memory structure, they will be also faster as a database query. Some details about the datastructures: carrierroute uses a trie, drouting a prefix tree (not looked deeply into drouting). In case of using a database directly, yes you will need to set the appropriate pseudo-variables by yourself. Cheers, Henning Am 10.09.19 um 10:43 schrieb Grant Bagdasarian: Correct me if I’m wrong but isn’t a linear list slower than a tree structure, due to the fact that it requires a full scan? Also, how does querying the database for routing information fit in these modules? It would require me to set the some kamailio routing variables like $du/$ru myself right? Thanks and regards, Grant On Tue, 10 Sep 2019 at 10:19, Henning Westerholt <hw@skalatan.de<mailto:hw@skalatan.de>> wrote: Am 10.09.19 um 10:08 schrieb Henning Westerholt: 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) somehow there is some content missing in the e-mail, In case of large route sets (like more than 10.000 up to a million entries) they can be queried faster as e.g. a linear list. 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 Am 10.09.19 um 09:59 schrieb Grant Bagdasarian: 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<mailto: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: -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org<mailto: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