Port locks with high time under LCNT

[Frank Muller]

Thanks to @Peti Gömöri, I was able to identify these Port locks:
https://gist.github.com/frankmullerl/008174c6594ca27584ac7f4e6724bee5

Some of them are taking up to 6.7sec (6707846 usec) :-/

My application is serving static images by calling file:sendfile/2 (
https://erlang.org/doc/man/file.html#sendfile-2).

Can someone please explain how I can avoid these locks or at least make
their impact lesser?

/Frank


Mon 30 dec. 2019 at 19:58, Frank Muller <frank.muller.erl@REDACTED> wrote:

> I was able to find out which lock is used by run_queue:
> https://gist.github.com/frankmullerl/008174c6594ca27584ac7f4e6724bee5
>
> Question: how can I check the lock behind #Port<app@REDACTED> for
> example?
>
> /Frank
>
> Hi All
>>
>> My custom-made web server which only serves only static files (a la Hugo:
>> https://gohugo.io/) is showing this under LCNT:
>> https://gist.github.com/frankmullerl/008174c6594ca27584ac7f4e6724bee5
>>
>> Can someone explain how to dig further to understand what’s going on and
>> why these Port locks are taking so much time?
>>
>> /Frank
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20200102/fd7c6674/attachment.htm>