Open aalirezamoradii opened 2 days ago
@vaind any ideas?
Memory: From my previous testing (because it's hard to tell without further details it's anything else): TraceEvent does a lot of temporary allocations on the heap during profiling and even though those do get freed, .net runtime keeps (and grows) the memory excessively as long as there's some available. Maybe you could try configuring GC limits if that's an option.
CPU: what is your configuration (TracesSampleRate
and ProfilesSampleRate
)? How many transactions are happening per second?
@vaind thank for your response
This is my sentry configuration
"Sentry": {
"Dsn": "dns@example.com/4",
"Release": "1.0.0",
"SendDefaultPii": true,
"MaxRequestBodySize": "Always",
"MinimumBreadcrumbLevel": "Debug",
"MinimumEventLevel": "Warning",
"AttachStackTrace": true,
"Debug": false,
"DiagnosticLevel": "Error",
"TracesSampleRate": 1.0,
"ProfilesSampleRate": 0.1
},
Transactions: 140 TPM in an hour period
Package
Sentry.AspNetCore
.NET Flavor
.NET
.NET Version
8.0.0
OS
Linux
SDK Version
4.13.0
Self-Hosted Sentry Version
24.10.0
Steps to Reproduce
in the .Net 8.0 (Microsoft.NET.Sdk.Web) Program.cs
Expected Result
Without using
o.AddIntegration(new ProfilingIntegration(TimeSpan.FromMilliseconds(500)));
Actual Result
After using
o.AddIntegration(new ProfilingIntegration(TimeSpan.FromMilliseconds(500)));
When start:
After 5 minutes: