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
{{ message }}
Repository navigation
Commit fc71cb7
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/introduction/performance.md
+8-5Lines changed: 8 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,7 @@ In rough order of what they return:
52
52
|---|---|---|
53
53
|[`opentelemetry_sampler`](configuration.md#opentelemetry), 1% ratio |~55 µs/req | 99% of your traces |
54
54
|`http_methods_to_capture=()` on the Sentry ASGI integrations |~35 µs/req | Sentry-side trace correlation |
55
-
|[`opentelemetry_exclude_spans`](configuration.md#opentelemetry), FastAPI and Litestar|~34 µs/req | the two ASGI event spans |
55
+
|[`opentelemetry_exclude_spans=["receive", "send"]`](configuration.md#opentelemetry), the default since 2.0|~34 µs/req | the two ASGI event spans |
56
56
|[`sentry_auto_session_tracking=False`](configuration.md#sentry), the default since 2.0 |~7.7 µs/req | Sentry release health |
57
57
|[`sentry_logging_breadcrumb_level=None`](configuration.md#sentry-logging-integration)|~7 µs per log record | log breadcrumbs on errors |
58
58
@@ -68,7 +68,7 @@ request, every request then pays the per-record cost measured here:
68
68
69
69
--8<-- "benchmarks/README.md:logging"
70
70
71
-
lite-bootstrap already applies five savings for you. It turns Sentry Logs off in the logging
71
+
lite-bootstrap already applies six savings for you. It turns Sentry Logs off in the logging
72
72
integration, because it never enables them and on 2.x the handler formats every record before
73
73
checking whether they are enabled; that one costs nothing. Since 2.0 it also leaves release-health
74
74
sessions off and starts breadcrumbs at `WARNING`, so an `INFO` record skips the breadcrumb handler.
@@ -78,8 +78,10 @@ back. And while Sentry tracing is off it reports request errors without sentry-s
78
78
integration, which costs you request transactions and bodies the handler never read; set `sentry_lean_error_capture=False` to keep the integration. With tracing off it also turns
0 commit comments