Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
A apachedex
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 2
    • Merge requests 2
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Commits
Collapse sidebar
  • nexedi
  • apachedex
  • Merge requests
  • !11

Merged
Created Dec 27, 2023 by Vincent Pelletier@vpelletierOwner

Compute and display median

  • Overview 0
  • Commits 2
  • Changes 2

Until now, what is reported is:

  • maximum query duration: unfortunately, with enough traffic there will always be outliers which are not representative of the normal user experience
  • average query duration: when maximum queries are orders of magnitude larger than the vast majority of queries (ex: hundreds of seconds vs. hundreds of milliseconds), it does not take many outliers to skew the average so much to be non-representative
  • score: this is more representative than the average query duration by eliminating the longest ones from the score

Adding a median allows giving a better idea of the query duration distribution. This is at the expense of a larger memory footprint, so make this support optional.

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: report_median
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7