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
[PROF-7307] Wire up allocation sampling into CpuAndWallTimeWorker
**What does this PR do?**
In #2657 we added support for the `Collectors::ThreadContext` to
sample a given object allocation.
But until now, triggering these kinds of allocations was only done in
our test suite.
This PR adds the missing part: actually sampling objects as Ruby
allocates them.
In the `Collectors::CpuAndWallTimeWorker`, we already
had a `TracePoint` that is called on every new object allocation
(`RUBY_INTERNAL_EVENT_NEWOBJ`), but we were only using it to
count allocations.
This PR changes the `TracePoint` code to actually call into the
`Collectors::ThreadContext` and thus allow allocation sampling to
happen.
**Motivation:**
This PR is another step towards the allocation profiling feature.
**Additional Notes:**
It's not yet possible to turn on allocation profiling via configuration.
I am reserving that change for later. But it's easy to do:
change the `profiling/component.rb` to use `alloc_samples_enabled: true`
and `allocation_sample_every: 1`.
This will result in a big overhead impact to the application. I'll be
working on this in later PRs.
In particular, the sampling approach we're using
(`allocation_sample_every`), is only a placeholder; it will get
replaced before we get to beta. This is why I don't want to add it
as a real user-available setting -- because it's temporary.
**How to test the change?**
This change includes test coverage. You can also manually check it out,
by following the instructions in the "Additional Notes".
(There's a feature flag needed for this data to show up in the
Datadog UX).
0 commit comments