[erlang-questions] start_timer and timer fired lag

Jesper Louis Andersen jesper.louis.andersen@REDACTED
Tue Mar 27 14:29:04 CEST 2018

Yes, that is the thing I'm talking about. Apart from long_schedule, I'd
also enable the other kinds of monitors, especially long_gc. Usually, when
the system reports one of these things, it is worth investigating why it is
doing so. A timer might also arrive late because a poor process has way too
much GC work to do, while also having too few cores. So having a marker for
this tend to be good infrastructure design.

IIRC, Fred's book "Erlang in Anger" also touches on this (but haven't
looked it up, I must admit).

On Tue, Mar 27, 2018 at 10:36 AM Alexander Petrovsky <askjuise@REDACTED>

> Leo, I think Jesper talk about
> http://erlang.org/doc/man/erlang.html#system_monitor-2
> вт, 27 марта 2018 г. в 5:04, Leo Liu <sdl.web@REDACTED>:
>> On 2018-03-26 15:35 +0000, Jesper Louis Andersen wrote:
>> > Enable the erlang system monitor and start looking for long schedules.
>> What are you referring to by "erlang system monitor"? First time hear
>> this and would like to try it out ;)
>> Cheers,
>> Leo
> --
> Петровский Александр / Alexander Petrovsky,
> Skype: askjuise
> Phone: +7 931 9877991 <+7%20931%20987-79-91>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20180327/eee30b99/attachment.htm>

More information about the erlang-questions mailing list