massemanet/eper

Opening About window with non-default ticktime takes long time

NAR opened this issue · 2 comments

NAR commented

I'm starting sherk this way:

$ erl -pa gtknode/lib/erlang/lib/gtknode-0.32/ebin -pa eper/lib/erlang/lib/eper-0.60/ebin -sname sherk -setcookie NETSim/var/tmp/ethanl/AAA -kernel net_ticktime 300 -kernel net_setuptime 100
Erlang R14B03 (erts-5.8.4) [smp:2:2] [rq:2] [async-threads:0] [kernel-poll:false]
[...]Eshell V5.8.4 (abort with ^G)
(sherk@eselivm2v47lmwp)1> sherk:go().
<0.49.0>
(sherk@eselivm2v47lmwp)2>
=INFO REPORT==== 5-Sep-2011::12:18:21 ===
in: {gtknode,handle_portdata,2}
portdata: "I am gtknode_sherk, you are sherk@eselivm2v47lmwp (14)\n"

=PROGRESS REPORT==== 5-Sep-2011::12:18:22 ===
supervisor: {local,inet_gethost_native_sup}
started: [{pid,<0.59.0>},{mfa,{inet_gethost_native,init,[[]]}}]

=PROGRESS REPORT==== 5-Sep-2011::12:18:22 ===
supervisor: {local,kernel_safe_sup}
started: [{pid,<0.58.0>},
{name,inet_gethost_native_sup},
{mfargs,{inet_gethost_native,start_link,[]}},
{restart_type,temporary},
{shutdown,1000},
{child_type,worker}]

Opening windows from the sherk GUI takes a long time, in the order of minutes (actually I thought windows can't be opened at all, it took so long time to appear). If I use the default net_ticktime and net_setuptime values, the GUI is fast. Unfortunately I have to use the non-default values, because this is what the application uses. Do you have any ideas why it's slow?

I'm using SuSE 10 SP2 on x86 and got both gtknode and sherk from the github repository on Friday (2011-09-02).

don't have a R14 node handy. will investigate.

was never able to reproduce.