Enable GC profiling when it's enabled in an app #879
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the app calls
GC::Profiler.enable
we will now automaticallycollect the Garbage Collection time for the Ruby VM magic dashboard.
We check if an app has enabled the GC profiler by calling
GC::Profiler.enabled?
. This operation is only checking a boolean valuein Ruby, which is also much faster the previous implementation of
checking the now removed
enable_gc_instrumentation
config option.Previously we had the undocumented
enable_gc_instrumentation
configoption, which called
GC::Profiler.enable
. We removed this in PR #876.We want to give developers more flexibility and allow to enable and
disable it at will. This way they can choose to only profile certain
parts of their app without having it enabled on app start.
Part of #868