[SERVER-85114] POC for configuring profiling and logging based on a match expression Created: 23/Aug/19 Updated: 12/Jan/24 Resolved: 05/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | James Wahlin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Query 2019-10-21, Query 2019-11-04, Query 2019-11-18, Query 2019-12-02, Query 2019-12-16, Query 2019-12-30, Query 2020-01-13, Query 2020-01-27, Query 2020-02-10, Query 2020-02-24, Query 2020-03-09 |
| Participants: |
| Comments |
| Comment by James Wahlin [ 05/Mar/20 ] |
|
Scoping effort will continue under WRITING-5000. The Cloud team will be involved early on and prior to final review so that we can confirm that we are all on the same page early on. (CC: rezwan.khan) |
| Comment by James Wahlin [ 05/Mar/20 ] |
|
I am closing this POC ticket as I think we have the information needed to move to scoping this project. Henrik's performance testing for the logging of "sample all" + "all slowms queries" showed that this would be possible without substantial overhead (as compared to just slowms). My POC work that confirmed that a MatchExpression filter on the entire system.profile record is prohibitively slow (roughly 5%) but should be feasible but only for a small subset of statistics. |
| Comment by David Storch [ 23/Aug/19 ] |
|
john.morales pawel.terlecki rezwan.khan andrew.davidson, I've scheduled this POC for the sprint ending on September 23. |