[Kamailio-Users] LCR With 300,000 Routes

[Geoffrey Mina]

Thanks for your answer.

I am using 1.5, so that's a good start!

In regards to preventing real time DB lookups... If I set my hash size
to 640K, and  I have 300K records in my routes table I will never need
to do a real time DB lookup?  How important is it to match the size of
the hashtable with the size of your routes table?  Will too much space
cause inefficiency?  I assume too little space would cause db lookups?

I have 8G of RAM available on this machine, so I am not concerned with
storing a lot of information in memory.

Thanks,
Geoff

On Mon, Mar 9, 2009 at 2:25 PM, Ovidiu Sas <osas at voipembedded.com> wrote:
> Carrierroute is able to handle this.
> The new lcr (1.5) should be able to handle this.  Make sure that you
> use a big hash table:
> http://www.kamailio.net/docs/modules/1.5.x/lcr#id2492264
>
> In both cases, avoid realtime db lookups if you want to be able to
> handle spikes of 100cps.
>
>
> Regards,
> Ovidiu Sas
>
> On Mon, Mar 9, 2009 at 2:19 PM, Geoffrey Mina <geoffreymina at gmail.com> wrote:
>> I have spec'd out how my LCR table would look based my current PSTN
>> gateway providers. Looks like I would need to load roughly 300,000
>> routes to properly represent everything.
>>
>> This server needs to be able to support spikes of 100 call setups per second.
>>
>> What is the general consensus on this?  And, if it's a No-Go, what
>> alternatives do I have?  I have looked briefly at the CarrierRoute
>> module, but haven't actually played with it.
>>
>> Thanks!
>> Geoff
>>
>> _______________________________________________
>> Kamailio (OpenSER) - Users mailing list
>> Users at lists.kamailio.org
>> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
>> http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
>>
>