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
We've seen a couple of requests to make DebugProbes feasible for testing/production/CI environments. While it can be acceptable even now (e.g. Ktor runs all tests using DebugProbes without a significant slowdown), for some workloads it generates too much allocation/native calls pressure. It would be nice to have a special (non-default!) mode that avoids this overhead
The text was updated successfully, but these errors were encountered:
qwwdfsad
changed the title
Provide a mode for DebugProbes that do not capture creation stacktrace
Provide a mode for DebugProbes that does not capture creation stacktrace
Jul 24, 2019
We've seen a couple of requests to make
DebugProbes
feasible for testing/production/CI environments. While it can be acceptable even now (e.g. Ktor runs all tests usingDebugProbes
without a significant slowdown), for some workloads it generates too much allocation/native calls pressure. It would be nice to have a special (non-default!) mode that avoids this overheadThe text was updated successfully, but these errors were encountered: