Hello Daniel, Here is the result with 1000 entries: I tried on pre-production only, I can't do this with production: shmem:fragments = 1 shmem:free_size = 733553288 shmem:max_used_size = 4644216 shmem:real_used_size = 4644216 shmem:total_size = 738197504 shmem:used_size = 3280576 Same server with all entries: shmem:fragments = 1 shmem:free_size = 463443800 shmem:max_used_size = 274753704 shmem:real_used_size = 274753704 shmem:total_size = 738197504 shmem:used_size = 80521648 And with all entries actually with production started since 4 hours: shmem:fragments = 53133 shmem:free_size = 60314640 shmem:max_used_size = 681270248 shmem:real_used_size = 677882864 shmem:total_size = 738197504 shmem:used_size = 243119832 Active registrations are around 200. There are also 325000 aliases. About call setups per second, based on the busiest day of the week, I see 95 CAPS. Regards, Igor. De : sr-users [mailto:sr-users-bounces@lists.sip-router.org] De la part de Daniel-Constantin Mierla Envoyé : jeudi 2 mars 2017 13:36 À : Kamailio (SER) - Users Mailing List &lt;sr-users(a)lists.sip-router.org&gt; Objet : Re: [SR-Users] Dimensioning of shared memory for carrierroute Hello, can you give the details for following two cases: 1) - start kamailio with only 1000 entries in carrier route - get output of 'kamctl stats shmem' 2) - start kamailio with all your entries in carrier route - get output of 'kamctl stats shmem' Then give also an estimation of how many active registrations and call setups per second you may have in average. Based on the difference and the estimations, we may be able to give more hints. Cheers, Daniel On 02/03/2017 12:23, Igor Potjevlesch wrote: Hello, I'd like to dimension shared memory to use "kamctl cr reload" without issue. Currently, my table "carrierroute" has 204k entries and if I do "kamctl cr reload", the reload fails. Just after, I have thousands of these errors: Mar 2 12:10:52 /usr/local/sbin/kamailio[28606]: ERROR: <core> [sip_msg_clone.c:507]: sip_msg_shm_clone(): cannot allocate memory Mar 2 12:10:52 /usr/local/sbin/kamailio[28606]: ERROR: tm [t_lookup.c:1332]: new_t(): ERROR: new_t: out of mem: Mar 2 12:10:52 /usr/local/sbin/kamailio[28606]: ERROR: tm [t_lookup.c:1472]: t_newtran(): ERROR: t_newtran: new_t failed After a reboot, Kamailio back to normal. Actually, I start Kamailio with -m 704 and -M 128. Thank you for your advises. Regards, Igor. _____ <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> www.avast.com _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list <mailto:sr-users@lists.sip-router.org> sr-users(a)lists.sip-router.org <http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla <http://www.twitter.com/miconda> www.twitter.com/miconda -- <http://www.linkedin.com/in/miconda> www.linkedin.com/in/miconda Kamailio Advanced Training - Mar 6-8 (Europe) and Mar 20-22 (USA) - <http://www.asipto.com> www.asipto.com Kamailio World Conference - May 8-10, 2017 - <http://www.kamailioworld.com> www.kamailioworld.com --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus