Re: [ns] How to reduce execution time of scenario generation (using setdest)

2009-02-28 Thread Mayur Mansukhlal Vegad


Thanks a lot Sriram!. It really cut the execution time drastically from
2.8 minutes to 0 (negligibly small number of) seconds.
Actually, I earlier avoided the God related statements, but it did not
help more. After I commented floyd_warshall and neighbour related
functions, it has reduced drastically.

regards,
Mayur

 this is sriram from iit kgp again

 in scenario gen ie setdest.cc you can delete unwanted portions which u may
 not use and this shuld reduce scenario generation time. like for my
 application i did not require functions like flloyd-warshall and the
 neighbour functions , god functions etc. remove them and ur scenario file
 generation shuld be faster. in the scenario file u basically require only
 lines for initial postion and setdest (set destination) neighbour
 reachable
 etc are discovered by the routing protocol themselves



 --
 B Sriram
 India
 mob : 09733706981



 Dear Mayur,

 Setdest has many nested for loops in which it is computing neighborhood of
 nodes, You remove all those nested loops as well. The actual code for
 generating random movement is not more that 50 lines. All other code is of
 god only. Previously when I worked with it, I did this optimization and it
 scalled well even for 1000 nodes(it generated the mobility scenario in
 less
 than 1 minute)

 I think this helps.

 regards,
 Manish



 On Sat, Feb 28, 2009 at 2:25 PM, Mayur Mansukhlal Vegad
 ma...@ee.iitd.ac.in
 wrote:

 I had already tried it by commenting the show_diffs() method call
 statement. But it didnot help. The only four statements printing God
 related stuff are those containing GOD_FORMAT and GOD_FORMAT2, which are
 inside the show_diffs() function. I commented that calling stmt. And the
 scenario file had no GOD stmts then. But still it takes similar amount
 of
 time.

 BTW thanks for your considerations!

 Mayur

  If you look at the code, setdest is spending most of the time in
  generating
  god entries. so if you are not interested in them, you can comment out
 the
  code which calculates and generates god entries which will reduce the
  execution time significantly.
 
  regards,
  Manish
 
  On Sat, Feb 28, 2009 at 1:06 AM, Mayur Mansukhlal Vegad
  ma...@ee.iitd.ac.in
  wrote:
 
 
  Dear all,
 
  scenario generation takes around 2.5 to 3 minutes for large number
 (eg
  100) of nodes. It is too much. After that the ns simulation takes
  another
  minute or more.
 
  Could anybody guide how to reduce the execution time particularly of
 the
  setdest tool?
 
  with regards,
  Mayur
 
 
 






[ns] How to reduce execution time of scenario generation (using setdest)

2009-02-27 Thread Mayur Mansukhlal Vegad

Dear all,

scenario generation takes around 2.5 to 3 minutes for large number (eg
100) of nodes. It is too much. After that the ns simulation takes another
minute or more.

Could anybody guide how to reduce the execution time particularly of the
setdest tool?

with regards,
Mayur