[SERVER-5905] Add data collection and command to get histogram of query response times Created: 23/May/12 Updated: 22/Mar/17 Resolved: 24/Jun/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, Performance |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.9 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Tad Marshall | Assignee: | Kevin Albertson |
| Resolution: | Done | Votes: | 5 |
| Labels: | neweng, performance | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Sprint: | Integrate+Tuning 16 (06/24/16), Integration 17 (07/15/16) | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
We should have instrumentation to characterize the overall workload and response time of a mongod or mongos server. A histogram with buckets with log base 2 microsecond resolution would be a nice start. Here's a straw man proposal: 1) For every request from a client, log the time it was received using the least expensive high resolution method. On Windows, this would be QueryPerformanceCounter(). Once the baseline functionality is working, we could consider doing this by database, by collection, by request type or by some other criterion. These would be additional instances of the same feature. There are a lot of things that we could learn by having this information: The better we can characterize workloads and our response to them, the better we can diagnose problems and propose solutions. All to the good. |
| Comments |
| Comment by Githook User [ 24/Jun/16 ] |
|
Author: {u'username': u'kevinAlbs', u'name': u'Kevin Albertson', u'email': u'kevin.albertson@10gen.com'}Message: |
| Comment by Githook User [ 24/Jun/16 ] |
|
Author: {u'username': u'kevinAlbs', u'name': u'Kevin Albertson', u'email': u'kevin.albertson@10gen.com'}Message: |
| Comment by Githook User [ 24/Jun/16 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: Revert " This reverts commit c7794350b056cdea85e1c6185a7dda4579936179. |
| Comment by Githook User [ 24/Jun/16 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: Revert " This reverts commit a22d2843ccab7f0333434d1124358c5c182427f6. |
| Comment by Kevin Albertson [ 23/Jun/16 ] |
|
We need to add a documentation page describing the operation latency histogram and its usage. |
| Comment by Githook User [ 23/Jun/16 ] |
|
Author: {u'username': u'kevinAlbs', u'name': u'Kevin Albertson', u'email': u'kevin.albertson@10gen.com'}Message: Signed-off-by: Kyle Suarez <kyle.suarez@mongodb.com> |
| Comment by Githook User [ 23/Jun/16 ] |
|
Author: {u'username': u'kevinAlbs', u'name': u'Kevin Albertson', u'email': u'kevin.albertson@10gen.com'}Message: Signed-off-by: Kyle Suarez <kyle.suarez@mongodb.com> |