Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recommend enabling auto_explain.log_timing #257

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

seanlinsley
Copy link
Member

On our production database we see around a 5% overhead from enabling auto_explain.log_timing. Since it's difficult to tell which parts of a complex query plan were actually slow without the per-node timing information, we've decided it's worth the overhead. As such, this PR updates the documentation to recommend enabling the setting while noting that users should judge for themselves if the overhead is worth it.

This PR also adds a Callout component that's been copied from the main app. Since we don't currently include Tailwind in the marketing site, this version has its styles inlined.

Screenshot 2024-05-10 at 10 11 55 AM
Screenshot 2024-05-10 at 10 13 31 AM

@seanlinsley seanlinsley requested a review from a team May 10, 2024 15:24
Copy link
Contributor

@msakrejda msakrejda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, though I think we need to update the README section given the public/private repo situation. We could either move this note to the pganalyze-web README or clarify that this is not possible for users outside of the pganalyze organization.

README.md Outdated Show resolved Hide resolved
components/PgSettingsRecommendations.tsx Show resolved Hide resolved
@seanlinsley
Copy link
Member Author

Holding off on merging so Lukas has time to review the change. If we want to provide more performance-focused guidance, we could also suggest setting sample_rate to 0.5 for example.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants