Megaco Avalanche! (was: ets:update_counter/3 taking a looooong time!)

[Micael Karlberg]

Hi,

Peter-Henry Mander writes:
 > Hi Micael,
 > 

<--- snip --->

 > 
 > Q2: The results were the same whether "hot" or "cold." I assume you are 
 > hinting at the garbage collector kicking in?

Actully I was thinking of making sure all code was loaded. But
GC is another possibillity.

<--- snip --->

 > 
 > If I manage to reproduce the symptoms with a subset of the code, would 
 > you be interested in reading it? I must warn you that it is *very* 
 > "experimental!" i.e. hacked code.

Yes.

 > 
 > Pete.

/BMK

 > 
 > Micael Karlberg wrote:
 > 
 > Hi Peter,
 > 
 > I have been trying to reproduce your problem without success.
 > I have some questions and suggestions.
 > 
 >    q1: Have you changed the max counter value (max_trans_id)?
 >        A small value would lead to reset_trans_id_counter more
 >        often (I admit that from the fprof output that does not
 >        seem to be the case).
 > 
 >    q2: The fprof results included here, where they produced
 >        after the system beeing "warmed up"?
 > 
 >    s1: When fprof'ing, use fprof:apply(Func, Args, OptionList)
 >        and include the megaco system processes megaco_config
 >        and megaco_monitor ({procs, [self(),megaco_config,megaco_monitor]}).
 > 
 >    s2: In order to get more reliable results, run more then one
 >        set of call-setup: N*(add, modify & subtract).
 > 
 >    s3: Try setting prio of the megaco_config process to high.
 > 
 > /BMK
 > 
 > 

-- 
Micael Karlberg          Ericsson AB, Älvsjö Sweden
Tel:  +46 8 727 5668     EAB/UHK/KD - OTP Product Development
ECN:  851 5668           Mail: micael.karlberg@REDACTED
Fax:  +46 8 727 5775