On Friday 10 April 2009, Juha Heinanen wrote:
I have been looking at the carrier route and LCR. it appears to me that LCR can be used to handle tariff , i.e, selecting lowest cost route. while carrier route doesn't have this capability at all. but carrier route , according to LCR, scales better than LCR.
what you mean by "according to LCR"? i'm not familiar with carrier route, but i don't see any other scaling limits with LCR except memory for lcr and gw entries.
perhaps carrier route does not keep its corresponding entries in memory, but fetches them each time from database?
Hi Juha,
no, it also keeps the entries in the memory, it don't do any run-time DB operations for normal routing. Perhaps the original poster referred to the pre 1.5.0 state, before your refactoring of the LCR code base. I'll see if i can update the cr README a bit.
Cheers,
Henning