[SERVER-39188] Allow profiling on mongos router Created: 25/Jan/19 Updated: 29/Jan/20 Resolved: 28/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | David Bartley | Assignee: | Andy Schwerin |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Even with --use-cpu-profiler, mongos reports "no such cmd" when running _cpuProfilerStart. |
| Comments |
| Comment by Andy Schwerin [ 29/Jan/20 ] |
|
We’ve had good luck with the Linux perf utility, which has a good profiling mode, and with Intel vTune. |
| Comment by David Bartley [ 29/Jan/20 ] |
|
What tools would you generally recommend to replace this functionality. |
| Comment by David Bartley [ 29/Jan/20 ] |
|
That's a bit unfortunate, since it's been effective at identifying/confirming a couple bugs ( |
| Comment by Andy Schwerin [ 28/Jan/20 ] |
|
We are removing support for the gperftools cpu profiler. We have found linux perf and other third party profilers more than adequate for studying the performance of mongodb in test environments, and maintaining support for these extra functionality was a minor ongoing burden. |
| Comment by Danny Hatcher (Inactive) [ 25/Jan/19 ] |
|
Hello David, Thank you for your report. I have forwarded this ticket to the appropriate team. Danny |