[DOCS-7703] Make our message surrounding the cost of profiling consistent. Created: 20/Apr/16 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ian Bentley | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-1769 |
| Description |
|
This page says: "When enabled, profiling has a minor effect on performance." While this page says: "Because the database profiler can negatively impact performance, only enable profiling for strategic intervals and as minimally as possible on production systems." Of course the full story is that "it depends". The first link is more optimistic, and can be wrong in cases where the profiling level is high, and write throughput is high. I'd suggest we aired on the side of caution and consistency, and advise to use profiling sparingly in production environments. |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |