Warning on High Response Time for Asynchronous Events

[n1nj444]

Issue Description

I've encountered a warning in the logs regarding high response times for handling asynchronous events, which may indicate that the CPU is starving.

Log Details

2024-05-03T08:45:35.906Z [WARNING] Your app's responsiveness to a new asynchronous event (such as a new connection, an upstream response, or a timer) was in excess of 100 milliseconds. Your CPU is probably starving. Consider increasing the granularity of your delays or adding more cedes. This may also be a sign that you are unintentionally running blocking I/O operations (such as File or InetAddress) without the blocking combinator.

Could you please guide me on where in the codebase I should look to address this issue? Any advice on modifications or configurations that could help resolve this warning would be greatly appreciated.

Thank you!

[nylonee]

This is likely because you've got a lot of things to "watchlist" and it's taking longer than your interval you set to sync everything. Try adding a couple of seconds to your sync interval.

[n1nj444]

Is this the correct parameter?

REFRESH_INTERVAL_SECONDS

I have set it to 120 seconds. What should I change it to in order to stop getting this warning log?

[nylonee]

Ah hmm, if it's set to 120 seconds then that wouldn't be the issue. I've usually seen this problem when it's set to 5 seconds or 10 seconds.

What are you running Watchlistarr on? Is it a raspberry pi?

[n1nj444]

I'm on a DS918+ (Synology) in a container with Docker

[n1nj444]

Bump

[nylonee]

Sorry, been a slow few weeks for me. I'm able to replicate this issue by reducing the number of CPUs my app uses, and setting the refresh to 10-ish seconds. Basically, I think this warning indicates that you don't have enough compute power to handle watchlistarr plus all the other things you have on your Synology. This may be continuous, or just during very specific times (e.g. when somebody starts transcoding and your CPU spikes to 100%).

There's more (very technical) information here

It's not a huge issue for Watchlistarr, because it will just handle the sync as fast as it can. There's not much else I can do around this so I'll close this ticket :)