You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/core/starvation-and-tuning.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,12 +3,14 @@ id: starvation-and-tuning
3
3
title: Starvation and Tuning
4
4
---
5
5
6
-
All Cats Effect applications constructed via `IOApp` have an automatic mechanism which periodically checks to see if the application runtime is starving for compute resources. If you ever see warnings which look like the following, they are the result of this mechanism automatically detecting that the responsiveness of your application runtime is below the configured threshold.
6
+
All Cats Effect applications constructed via `IOApp` have an automatic mechanism which periodically checks to see if the application runtime is starving for compute resources. If you ever see warnings which look like the following, they are the result of this mechanism automatically detecting that the responsiveness of your application runtime is below the configured threshold. Note that the timestamp is the time when the starvation was detected, which is not precisely the time when starvation (or the task that is responsible) began.
7
7
8
8
```
9
-
[WARNING] Your CPU is probably starving. Consider increasing the granularity
10
-
of your delays or adding more cedes. This may also be a sign that you are
11
-
unintentionally running blocking I/O operations (such as File or InetAddress)
9
+
2023-01-28T00:16:24.101Z [WARNING] Your app's responsiveness to a new asynchronous
10
+
event (such as a new connection, an upstream response, or a timer) was in excess
11
+
of 40 milliseconds. Your CPU is probably starving. Consider increasing the
12
+
granularity of your delays or adding more cedes. This may also be a sign that you
13
+
are unintentionally running blocking I/O operations (such as File or InetAddress)
0 commit comments