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
@kaiohenrique which version of Npgsql are you using? Assuming it's a modern version (i.e. 6.0), the only use of event pipe should be via the event counters which Npgsql emits - but these should be very efficient and definitely have almost no overhead, especially if you haven't actually registered to receive them (e.g. with dotnet counters).
If you're using Npgsql 6.0 and aren't listening to event counters, can you submit a minimal code sample where you're seeing such an overhead?
Is it possible to disable diagnostics tracing to workaround any possible overhead it could cause to our application?
The text was updated successfully, but these errors were encountered: