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

Add support for profiling via pprof #593

Merged
merged 1 commit into from
Feb 3, 2025
Merged

Add support for profiling via pprof #593

merged 1 commit into from
Feb 3, 2025

Conversation

evenh
Copy link
Member

@evenh evenh commented Feb 3, 2025

Disabled by default in case we're incurring a performance hit

Summary by CodeRabbit

  • New Features
    • Introduced performance profiling support for enhanced monitoring and diagnostics.
    • Profiling can now be activated via an environment configuration, enabling a dedicated endpoint for runtime performance insight.

Disabled by default in case we're incurring a performance hit
@evenh evenh requested a review from a team as a code owner February 3, 2025 09:00
@evenh evenh requested review from Griznah, omaen and BardOve February 3, 2025 09:00
Copy link
Contributor

coderabbitai bot commented Feb 3, 2025

Walkthrough

The changes enhance the application's profiling capabilities. In cmd/skiperator/main.go, the import statements are reorganized and a new variable pprofBindAddr is introduced, conditionally set for profiling based on a flag. The manager initialization now accepts a profiling bind address option. In pkg/flags/flags.go, a new boolean field EnableProfiling is added to the Features struct and is initialized using an environment variable. Error handling and logging remain largely unchanged.

Changes

File(s) Change Summary
cmd/skiperator/main.go Reorganized import statements; introduced pprofBindAddr variable which conditionally sets to ":8281"; updated ctrl.NewManager call to include profiling option.
pkg/flags/flags.go Added EnableProfiling boolean field to the Features struct; updated initialization to set this field based on the ENABLE_PROFILING environment variable.

Sequence Diagram(s)

sequenceDiagram
    participant Env as Environment
    participant F as Flags Init
    participant M as Main
    participant CM as Manager (ctrl.NewManager)

    Env->>F: Read ENABLE_PROFILING variable
    F-->>M: Return EnableProfiling (true/false)
    M->>M: Set pprofBindAddr = ":8281" if profiling enabled
    alt Profiling Enabled
        M->>CM: Initialize Manager with PprofBindAddress = ":8281"
    else
        M->>CM: Initialize Manager without PprofBindAddress
    end
Loading

Poem

I'm a rabbit of code, hopping with delight,
Profiling's enabled, making our system shine bright.
Imports now sorted, with paths clear and neat,
Flags guide the way, steady and sweet.
Hop along through the code, with a joyful little beat!
🐇✨
Every change makes our app a treat!

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

github-actions bot commented Feb 3, 2025

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails

Scanned Files

@evenh evenh requested a review from larsore February 3, 2025 09:00
Copy link
Contributor

@omaen omaen left a comment

Choose a reason for hiding this comment

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

Still only accessible by port forward right?

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (2)
pkg/flags/flags.go (1)

17-17: LGTM! Consider adding field-level documentation.

The new EnableProfiling field follows the existing patterns and conventions. Consider adding a field-level comment to document its purpose and the environment variable that controls it.

 type Features struct {
 	DisablePodTopologySpreadConstraints bool
+	// EnableProfiling enables runtime profiling via pprof when set to true.
+	// Controlled by SKIPERATOR_ENABLE_PROFILING environment variable.
 	EnableProfiling                     bool
 }
cmd/skiperator/main.go (1)

73-76: Document the hardcoded port number.

The pprof port (8281) should be documented to explain why this specific port was chosen and to make it easier to find and update if needed.

-	pprofBindAddr := ""
-	if flags.FeatureFlags.EnableProfiling {
-		pprofBindAddr = ":8281"
-	}
+	// Port 8281 is reserved for pprof profiling to avoid conflicts with other ports:
+	// - 8081: Health probe
+	// - 8181: Metrics
+	pprofBindAddr := ""
+	if flags.FeatureFlags.EnableProfiling {
+		pprofBindAddr = ":8281"
+	}
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 08115ab and fb190b4.

📒 Files selected for processing (2)
  • cmd/skiperator/main.go (2 hunks)
  • pkg/flags/flags.go (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Build and run tests
  • GitHub Check: Build and run tests
🔇 Additional comments (2)
pkg/flags/flags.go (1)

23-23: LGTM! The initialization follows existing patterns.

The field is properly initialized using the same helper function and follows the environment variable naming convention.

cmd/skiperator/main.go (1)

85-85: LGTM! The pprof configuration is properly integrated.

The pprof binding address is correctly passed to the manager configuration.

@evenh
Copy link
Member Author

evenh commented Feb 3, 2025

That's correct @omaen. It is only accessible if we port-forward to that port or expose it via a Service/Istio – which we don't do today.

@evenh evenh enabled auto-merge February 3, 2025 09:19
Copy link
Contributor

@martinhny martinhny left a comment

Choose a reason for hiding this comment

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

cool

@evenh evenh merged commit bd6bdb5 into main Feb 3, 2025
10 checks passed
@evenh evenh deleted the add-pprof branch February 3, 2025 09:19
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.

3 participants