On Sunday 07 August 2011, Yaron Nachum wrote: Hello Yaron, It should be possible to use cr with several million of entries, just keep in mind to increase the shared memory settings somewhat, 1024MB should be probably a good start. I know from some reports that people use it successfully in a scenario with millions of entries as well. Its of course possible to do the data reloading during traffic, you'll just need the double amount of RAM. ;-) The reason for this is that the module discard the old data only after the successful loading of the new data. The PDB module is from the setup a bit more complicated, but has lower performance requirements and can be placed on a dedicated server. It was written especially for number portability. Basically it works that you setup the server module (pdbd) on some machine and feed it with a precompiled data file. There is a small compiler (pdbt) to create this mapping file from text data. You then use the pdb module in your configuration to get the carrier ID for a number and do your routing accordingly in the script, e.g. with cr. You find the tool in the utils/pdbt dir in sr. But for the performance requirements you quoted I'd look also into another scenario - what about just storing this data in a "normal" database and querying it with sqlops? If you give the DB enough RAM it should be also fast enough. Best regards, Henning