Yet another weird ns-3 execution time

5 views
Skip to first unread message

Providence SALUMU MUNGA

unread,
Oct 2, 2008, 6:18:54 PM10/2/08
to ns-3-users, Providen...@gmail.com
Dear all,

Late this night, I executed the "simple-alternate-routing" script from
ns-3-dev/example. This run endlessly and I finally was obliged to kill
the process.

The output of htop for the relevant process was as follows (Notice how
huge the amount of used memory is!!!):
VIRT --- RES --- SHR --- CPU% --- MEM% ----- TIME+
1905M 1202M 7920 91.0 59.9 10:13.76

I'm not very good at profiling unix processes, so I couldn't check to
see where the problem came from. Would you please run this script
and confirm this weird behavior?

Many thanks in advance,

--
Providence SALUMU M.

Doctorant, Département Logiciels-Réseaux
TELECOM SudParis
9 rue Charles Fourier, 91011 Evry Cedex

Tel: +33 1 60 76 44 65
Mob: +33 6 84 54 94 85
Fax: +33 1 60 76 47 11
http://www-lor.int-evry.fr/

"If you can't be strong, be clever, and make peace with someone who is
strong. But it's always better to be strong yourself! Always!" -- B.O.
LowLow.

Tom Henderson

unread,
Oct 2, 2008, 7:47:39 PM10/2/08
to ns-3-users, Providen...@gmail.com

>-----Original Message-----
>From: Providence SALUMU MUNGA [mailto:psa...@gmail.com]
>Sent: Thursday, October 2, 2008 02:18 PM
>To: 'ns-3-users', Providen...@gmail.com
>Subject: Yet another weird ns-3 execution time
>
>
>Dear all,
>
>Late this night, I executed the "simple-alternate-routing" script from
>ns-3-dev/example. This run endlessly and I finally was obliged to kill
>the process.
>
>The output of htop for the relevant process was as follows (Notice how
>huge the amount of used memory is!!!):
>VIRT --- RES --- SHR --- CPU% --- MEM% ----- TIME+
>1905M 1202M 7920 91.0 59.9 10:13.76
>
>I'm not very good at profiling unix processes, so I couldn't check to
>see where the problem came from. Would you please run this script
>and confirm this weird behavior?

This was a typo in that script; Stop() was never called, but Start() was instead called twice. I checked in a fix.

Thanks,
Tom

Reply all
Reply to author
Forward
0 new messages