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: articles/cosmos-db/sql/performance-tips-dotnet-sdk-v3-sql.md
+41-1Lines changed: 41 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: j82w
5
5
ms.service: cosmos-db
6
6
ms.subservice: cosmosdb-sql
7
7
ms.topic: how-to
8
-
ms.date: 07/08/2021
8
+
ms.date: 01/25/2022
9
9
ms.author: jawilley
10
10
ms.devlang: csharp
11
11
ms.custom: devx-track-dotnet, contperf-fy21q2
@@ -61,6 +61,46 @@ If you're testing at high throughput levels, or at rates that are greater than 5
61
61
> [!NOTE]
62
62
> High CPU usage can cause increased latency and request timeout exceptions.
63
63
64
+
## <aid="logging-and-tracing"></a> Logging and tracing
65
+
66
+
Some environments have the [.NET DefaultTraceListener](/dotnet/api/system.diagnostics.defaulttracelistener) enabled. The DefaultTraceListener poses performance issues on production environments causing high CPU and I/O bottlenecks. Check and make sure that the DefaultTraceListener is disabled for your application by removing it from the [TraceListeners](/dotnet/framework/debug-trace-profile/how-to-create-and-initialize-trace-listeners) on production environments.
67
+
68
+
Latest SDK versions (greater than 3.23.0) automatically remove it when they detect it, with older versions, you can remove it by:
0 commit comments