On Tuesday 20 July 2010, Iñaki Baz Castillo wrote:
this is the option added to overcome the MI design limitations - while most of dumped structures are in shared memory, MI builds the output in PKG memory, resulting in insufficient space since shm is much bigger than pkg - also this sometime ended as well in lot of mem fragmentation for mi process in the past.
Hi Elena. This is also I'm a bit afraid of when using MI command to manage large ammount of records (LCR, locations, 'address' entries...). Wouldn't make sense MI to use shared memory instead of private memory?
Hi Iñaki,
this would be possible, but its IMHO a bit wrong from a conceptional POV. This FIFO command execution belongs to the MI process, and it should not affect the working of other process which are busy routing SIP requests - they don't need to see this as all. One workaround is as discussed is to just use system malloc, another would be to partition the command execution in small steps like we do for data loading in several modules.
But as i said earlier, its maybe not the best idea in general to pipe the output of several houndred thousands rules through the MI interface, especially if the information is available more or less similar in the database.
Regards,
Henning