[SERVER-24338] In-memory data structures for latency histogram Created: 01/Jun/16  Updated: 05/Apr/17  Resolved: 13/Jun/16

Status: Closed
Project: Core Server
Component/s: Diagnostics, Internal Code
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Kyle Suarez Assignee: Kevin Albertson
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Integrate+Tuning 15 (06/03/16), Integrate+Tuning 16 (06/24/16)
Participants:

 Description   

We need to design in-memory data structures for the operation latency histogram and find an appropriate place to store them.

These data structures include (but might not be limited to)

  • an actual histogram class with a fast increment operation
  • a namespace-to-histogram map
  • a command name-to-histogram type map (i.e. is this a read/write/command)


 Comments   
Comment by Kyle Suarez [ 13/Jun/16 ]

Proof-of-concept is complete and code/reviews will be tracked in SERVER-5905.

Comment by Kyle Suarez [ 01/Jun/16 ]

We'll also have to consider the locking on these data structures:

  • The global histogram can have its own lock.
  • Collection-level histograms will probably need some sort of collection lock. For write operations, we'll already have an X or IX lock; for read operations it might be trickier.
Generated at Thu Feb 08 04:06:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.