Unfortunately the code is not open sourced. I looked through it again and
couldn't find any timers with timeouts longer than a few minutes. I'll
follow up if I find something else. Thanks for your help!
On Wednesday, October 19, 2016 at 9:09:51 AM UTC-7, rhys.h...@gmail.com
wrote:
>
> I'm not s
I'm not sure. You mention that there's only a single mDNS query per minute,
so the five-second timeouts would never overlap.
Looking at the profile again, a lot of the time seems to be spent on the
locks involved in sleeping for some amount of time. This makes it seem like
there are a lot of ac
Although what you are saying makes a lot of sense(thanks!), I see that my
program is just using a 5 second timeout. Is it possible that it can still
lead to this performance profile?
On Tuesday, October 18, 2016 at 10:22:09 AM UTC-7, rhys.h...@gmail.com
wrote:
>
> Does your program set a very
Does your program set a very large Timeout on its mdns requests (maybe tens
of hours long)?
It looks like your program is consuming a lot of CPU cycles on managing
timers. On the left half of the flame graph, lots of CPU cycles are spent
in runtime.timerproc. Time here indicates a large number
