@lbalaceanu - do you have any remarks on this report? Any change to carrierroute module that you are aware of and may result in such behaviour? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2653#issuecomment-787904218

For reference, the same issue was reported in #2613 -- referencing it here, as it provides some other details that could be useful for troubleshooting. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2653#issuecomment-794134148

Hallo. We have difficulties in reproducing this. We have ~500.000 entries in the carrierroute table and it does not take so long for us to load them. The difference is, we are using MariaDB (not Postgres). Maybe @kristina258 can tell what DB engine was used in the previous bug report? We are not sure whether it is a DBengine issue or some kind of special table content. Do you maybe have many entries where where the prob is set 0? Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 1411 Server version: 10.3.27-MariaDB-0+deb10u1-log Debian 10 Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [ser]> **select count(*) from carrierroute;** +----------+ | count(*) | +----------+ | **501684** | +----------+ 1 row in set (0.000 sec) MariaDB [ser]> Bye test-proxy2-bs ~ # **time kamcmd cr.reload_routes** real **0m35.289s** user 0m0.005s sys 0m0.000s test-proxy2-bs ~ # **kamailio -v** version: **kamailio 5.3.8** (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: compiled with gcc 8.3.0 test-proxy2-bs ~ # **grep -r " and prob>0" /var/log/mysql/mysql.log** 210310 11:18:49 27 Query SELECT * FROM carrierroute WHERE carrier=9101 and domain=5 and prob>0 27 Query SELECT * FROM carrierroute WHERE carrier=9101 and domain=6 and prob>0 27 Query SELECT * FROM carrierroute WHERE carrier=9101 and domain=7 and prob>0 27 Query SELECT * FROM carrierroute WHERE carrier=9101 and domain=0 and prob>0 27 Query SELECT * FROM carrierroute WHERE carrier=9101 and domain=1 and prob>0 27 Query SELECT * FROM carrierroute WHERE carrier=9101 and domain=2 and prob>0 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2653#issuecomment-795223278

Thank you for fast reply. We will follow this path first and adapt our entries. We keep you informed. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2653#issuecomment-795243126

Hi @NiteCrwlr , just pushed commit 087c00a276623adad6b87242bc58f7c0b4d8ff33 as a possible fix for this bug. For us it worked since we were able to reproduce the situation by having a lot of entries in the carrierroute table with prob = 0. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2653#issuecomment-797594239

Hi @kristina258, I will try to reproduce with postgres and will come back to you. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2653#issuecomment-800183303

@kristina258 the problem seems to be fixed now for another reporter with the bug fix done. Can you maybe double check if you included the correct commit in your test setup? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2653#issuecomment-800959360

I tested the commit again, don't know if it helps: One with prob 0: count | prob -------+------ 12822 | 0 3 | 0.5 6 | 0.01 30102 | 1 And one with prob 999: count | prob -------+------ 12822 | 999 3 | 0.5 6 | 0.01 30102 | 1 Same result in startup speed, around 17s. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2653#issuecomment-802709338

Hi @lbalaceanu, probably you reproduced it. You had about 500 000 records in carrierroute table and it tooks to load 52s. I have about 1 700 000 and it took 3min. 3 times more records so the loading time is 3 times higher. When I run kamailio on debian 8 with kamailio version 4.4.7 with the same DB and same carrierroute records it took to load aproximetly 20s. I would like to kindly ask you, if it is possible for you to perform the test with kamailio version 4.4.7 and then check the time carrierroute needed for reloading. Thank you for your patience. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2653#issuecomment-805117076

Hi @kristina258, I have also tried with kamailio 4.4 but unfortunately this time I get 1min7 secs for the approx 500k entries in carrierroute tables created with kamdbctl tool. I don't know if I am doing something wrong as I don't have experience with postgres, but for me kamailio dev vs kamailio 4.4 are more ore less similar as far as load times are involved. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2653#issuecomment-809358264

Closed #2653. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2653#event-4539890510