Project

General

Profile

Feature #4903

OpTracker: support hierarchies of request classes

Added by Greg Farnum over 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
common
Target version:
-
Start date:
05/03/2013
Due date:
% Done:

0%

Source:
Development
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

Right now, a TrackedOp is associated with an OpTracker, and all our statistics come out of that. It would be nice if we could define hierarchies of ops and then get statistics at arbitrary granularities. For instance:
MDS
MDS::heartbeat
MDS::TableRequest
Client
Client::caps
Client::request
Client::request::write
Client::request::read

At present we have to settle for doing very coarse partitioning by simply creating the TrackedOp out of a different OpTracker when it comes in.

Also available in: Atom PDF