-
- Downloads
Track method call times/counts as a single metric
Previously we'd create a separate Metric instance for every method call that would exceed the method call threshold. This is problematic because it doesn't provide us with information to accurately get the _total_ execution time of a particular method. For example, if the method "Foo#bar" was called 4 times with a runtime of ~10 milliseconds we'd end up with 4 different Metric instances. If we were to then get the average/95th percentile/etc of the timings this would be roughly 10 milliseconds. However, the _actual_ total time spent in this method would be around 40 milliseconds. To solve this problem we now create a single Metric instance per method. This Metric instance contains the _total_ real/CPU time and the call count for every instrumented method.
Showing
- CHANGELOG 1 addition, 0 deletionsCHANGELOG
- doc/development/instrumentation.md 2 additions, 17 deletionsdoc/development/instrumentation.md
- lib/gitlab/metrics/instrumentation.rb 2 additions, 17 deletionslib/gitlab/metrics/instrumentation.rb
- lib/gitlab/metrics/method_call.rb 52 additions, 0 deletionslib/gitlab/metrics/method_call.rb
- lib/gitlab/metrics/transaction.rb 30 additions, 5 deletionslib/gitlab/metrics/transaction.rb
- spec/lib/gitlab/metrics/instrumentation_spec.rb 4 additions, 6 deletionsspec/lib/gitlab/metrics/instrumentation_spec.rb
- spec/lib/gitlab/metrics/method_call_spec.rb 91 additions, 0 deletionsspec/lib/gitlab/metrics/method_call_spec.rb
- spec/lib/gitlab/metrics/transaction_spec.rb 16 additions, 0 deletionsspec/lib/gitlab/metrics/transaction_spec.rb
lib/gitlab/metrics/method_call.rb
0 → 100644
spec/lib/gitlab/metrics/method_call_spec.rb
0 → 100644
Please register or sign in to comment