A memory consumption problem occured in recent simulations (cmcast-[150,200,250].tcl), so we decided to take a closer look at scaling issue. See page http://www-mash.cs.berkeley.edu/ns/ns-scaling.html which demostrates the efforts in finding the bottlneck.
The following table summarises the results of investigating the
|KBytes||cmcast-50.tcl(217 Links)||cmcast-100.tcl(950 Links)|
|turn off trace-all||5,095||15,465|
|remove unnecessay variables||5,087||15,451|