[SERVER-30535] Consistent names for ServiceExecutorAdaptive metrics Created: 07/Aug/17  Updated: 30/Oct/23  Resolved: 16/Aug/17

Status: Closed
Project: Core Server
Component/s: Diagnostics
Affects Version/s: 3.5.11
Fix Version/s: 3.5.12

Type: Improvement Priority: Major - P3
Reporter: Bruce Lucas (Inactive) Assignee: Andrew Morrow (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Platforms 2017-08-21
Participants:

 Description   

The state of a task between being scheduled and being executed is variously referred to as "scheduled", "queued", and "pending"; it would be helpful for understanding to use a single term. (This ticket is about the user-visible metric names, but it might also be helpful to use consistent naming in the code).

Specifically, the following metrics relate to executing tasks:

  • totalExecuted
  • tasksExecutng
  • totaltimeExecutingMicros

Whereas the comparable metrics relating to the queued tasks are named as follows

  • totalScheduled
  • queueDepth
  • totalTimeQueuedMicros

To make these consistent and easier to understand propose the following changes:

  • totalScheduled -> totalQueued
  • queueDepth -> tasksQueued


 Comments   
Comment by Githook User [ 16/Aug/17 ]

Author:

{'username': 'acmorrow', 'email': 'acm@mongodb.com', 'name': 'Andrew Morrow'}

Message: SERVER-30527 SERVER-30529 SERVER-30535 Fixup stats for adaptive executor
Branch: master
https://github.com/mongodb/mongo/commit/f5a7735f92136611b3158d8185727d540df8e94d

Generated at Thu Feb 08 04:24:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.