Open
Description
Problem Statement
Cache spans are turned off by default for Django cache due to performance issues described in #2122
Recent load testing showed that cache spans did not introduce significant overhead, granted in a clean room environment, #3058
Proposal
We should turn on cache spans by default, as it will allow more sentry users to get value out of cache insights.
However, before doing so, we should find a suitably high traffic deployment to validate the findings in #3058.
Solution Brainstorm
Are there any other ways we could detect that emitting cache spans is creating too much load on a system and disable cache spans, rather than defaulting cache_spans=False, i.e., disable cache spans if a certain volume of traffic is hit, rather than by default:
high_volume_cache_spans=False