[SERVER-81065] Cache the hash of the client metadata to speed up query stats computation Created: 14/Sep/23 Updated: 29/Oct/23 Resolved: 22/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Alyssa Clark |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Integration
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Description |
|
For some of our smallest/quickest queries the client metadata is actually a big portion of the query stats store key, and we recompute the hash on every query to detect whether we've seen it before. The Client object lives as long as the client connection, so we should only need to compute this hash once per Client - which should be a lot more performant. |
| Comments |
| Comment by Githook User [ 21/Sep/23 ] |
|
Author: {'name': 'Alyssa Wagenmaker', 'email': 'alyssa.wagenmaker@mongodb.com', 'username': 'awagenmaker'}Message: |