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
The output of the which is a list of the top 4 contributors to performance issues. For example, the output of the command will be something like the following:
112
+
The output is a list of the top four contributors to performance issues. For example, the output of the command is something like the following:
113
113
114
114
```console
115
115
=====================================
@@ -143,19 +143,20 @@ The following steps can be used to troubleshoot and mitigate these issues:
143
143
=====================================
144
144
```
145
145
146
-
To improve the performance of Defender for Endpoint on Linux, locate the one with the highest number under the `Total files scanned` row and add an antivirus exclusion for it (carefully evaluate if it is safe to exclude). For more information, see [Configure and validate exclusions for Defender for Endpoint on Linux](linux-exclusions.md).
146
+
To improve the performance of Defender for Endpoint on Linux, locate the one with the highest number under the `Total files scanned` row and add an antivirus exclusion for it (carefully evaluate if it's safe to exclude). For more information, see [Configure and validate exclusions for Defender for Endpoint on Linux](linux-exclusions.md).
147
147
148
148
> [!NOTE]
149
-
> The application stores statistics in memory and only keeps track of file activity since it was started and real-time protection was enabled. Processes that were launched before or during periods when real time protection was off are not counted. Additionally, only events which triggered scans are counted.
149
+
> The application stores statistics in memory and only keeps track of file activity since it was started and real-time protection was enabled. Processes that were launched before or during periods when real time protection was off aren't counted. Additionally, only events which triggered scans are counted.
150
150
151
151
## Troubleshoot performance issues using Hot Event Sources
152
152
153
153
**Applies to:**
154
154
- Performance issues in files and executables which are consuming most CPU cycles in the entire filesystem.
155
155
156
156
Hot event sources is a feature that allows customers to identify which process or directory is responsible for high resource consumption. To investigate which process/executable is generating the most noise, follow these steps.
157
-
> [!NOTE]
158
-
> These commands require you to have root permissions. Ensure that sudo can be used.
157
+
158
+
> [!NOTE]
159
+
> These commands require you to have root permissions. Ensure that sudo can be used.
159
160
160
161
First, check the log level on your machine.
161
162
@@ -284,7 +285,7 @@ Once you've finished the investigation, you can change the log level back to "in
284
285
Log level configured successfully
285
286
```
286
287
287
-
To improve the performance of Defender for Endpoint on Linux, locate the path with the highest number in the count row and add a global process exclusion (if it's an executable) or a global file/folder exclusion (if it's a file) for it (carefully evaluate if it is safe to exclude). For more information, see [Configure and validate exclusions for Defender for Endpoint on Linux](linux-exclusions.md).
288
+
To improve the performance of Defender for Endpoint on Linux, locate the path with the highest number in the count row and add a global process exclusion (if it's an executable) or a global file/folder exclusion (if it's a file) for it (carefully evaluate if it's safe to exclude). For more information, see [Configure and validate exclusions for Defender for Endpoint on Linux](linux-exclusions.md).
288
289
289
290
## Troubleshoot performance issues using eBPF Statistics
290
291
@@ -320,9 +321,10 @@ To collect current statistics using eBPF statistics, run:
320
321
288 : 19
321
322
41 : 15
322
323
```
324
+
323
325
This command monitors the system for 20 seconds and shows the results. Here the top initiator path (postgresql/12/bin/psql) shows the path of the process that generated the most system calls.
324
326
325
-
To improve the performance of Defender for Endpoint on Linux, locate the one with the highest `count` in the `Top initiator path` row and add a global process exclusion for it (carefully evaluate if it is safe to exclude). For more information, see [Configure and validate exclusions for Defender for Endpoint on Linux](linux-exclusions.md).
327
+
To improve the performance of Defender for Endpoint on Linux, locate the one with the highest `count` in the `Top initiator path` row and add a global process exclusion for it (carefully evaluate if it's safe to exclude). For more information, see [Configure and validate exclusions for Defender for Endpoint on Linux](linux-exclusions.md).
326
328
327
329
## Configure Global Exclusions for better performance
0 commit comments