[SERVER-49055] Report additional usage metrics from Biggie in the 'serverStatus' command Created: 24/Jun/20  Updated: 29/Oct/23  Resolved: 16/Jul/20

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.7.0

Type: New Feature Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Yuhong Zhang
Resolution: Fixed Votes: 0
Labels: intern_ephemeral_for_test
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-49198 Implement ServerStatusSection for Biggie Closed
is depended on by SERVER-49008 Create a new jstest to track Biggie's... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-07-13, Execution Team 2020-07-27
Participants:

 Description   

The serverStatus command allows storage engines to append custom statistics to the output via the ServerStatusSection interface. We can use this to report additional Biggie metrics such as:

  1. Reporting to the total memory usage of the radix trees still available in the history. We'll have to watch out to avoid double counting shared nodes between the trees. Today, Biggie only tracks the size of the stored values in data nodes only.
  2. The average number of child nodes that each parent has. With the adaptive node work, this should decrease from 256 dramatically.

 



 Comments   
Comment by Githook User [ 16/Jul/20 ]

Author:

{'name': 'Yuhong Zhang', 'email': 'danielzhangyh@gmail.com', 'username': 'YuhongZhang98'}

Message: SERVER-49055 Report additional usage metrics from Biggie in the 'serverStatus' command
Branch: master
https://github.com/mongodb/mongo/commit/67db847b2b833a6df876a951ec8c08872d567008

Comment by Gregory Wlodarek [ 29/Jun/20 ]

A nice approach for tracking the memory usage would be to increment/decrement an atomic number when the Node constructor/destructors are called.
One edge case that we'll need to consider for this is updating uniquely owned nodes data.

Generated at Thu Feb 08 05:18:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.