BigW Consortium Gitlab

  1. 09 Nov, 2016 1 commit
  2. 12 Sep, 2016 1 commit
  3. 17 Jun, 2016 1 commit
    • Track method call times/counts as a single metric · be3b8784
      Yorick Peterse authored
      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.
  4. 16 Jun, 2016 2 commits
  5. 14 Jun, 2016 2 commits
  6. 03 Jun, 2016 2 commits
  7. 05 May, 2016 1 commit
  8. 11 Apr, 2016 2 commits
  9. 06 Apr, 2016 1 commit