Add analyzer performance page

[connie-ooi]

Add Analyzer performance page.

Resolves #6924

[gemini-code-assist]

Summary of Changes

Hello @connie-ooi, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a comprehensive guide to help users diagnose and resolve performance issues with the Dart analysis server. It aims to improve the developer experience by offering solutions to common problems and providing clear steps for reporting more complex issues, ensuring that users can efficiently troubleshoot their development environments.

Highlights

• New Documentation Page: A new page titled 'Troubleshoot Analyzer Performance' has been added to provide guidance on diagnosing and resolving common Dart analysis server performance issues.
• Known Performance Issues: The new page details common performance bottlenecks, including the impact of security software on Windows systems and issues related to symbolic links in package directories.
• Reporting Unknown Issues: Instructions are provided on how to effectively report unknown performance problems to the Dart SDK issue tracker, emphasizing the importance of reproduction steps, performance data collection, and instrumentation logs.
• Navigation Integration: The new 'Troubleshoot Analyzer Performance' page has been integrated into the site's sidebar navigation under the 'Tools' section.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds a new documentation page for troubleshooting Dart analyzer performance, which is a valuable addition. The content is clear and helpful. My review focuses on several formatting issues in the new markdown file, primarily related to adhering to the 80-character line limit specified in the contribution guidelines. I've provided specific suggestions to resolve these style guide violations.

[dart-github-bot]

Visit the preview URL for this PR (updated for commit 6c26b36):

https://dart-dev--pr7020-analyzer-performance-0mqpdan0.web.app

[bwilkerson]

Fantastic, thanks!

[parlough]

Overall looks great to me. We've needed this for a while, so thanks for tackling it!

Do wait for a copy review from @antfitch.

[parlough]

Thanks for making those adjustments, still looks good to me!

A question though. Should we link to this from the https://dart.dev/tools/analysis page for more discoverability? At least in the end Resources section but perhaps as a note somewhere else as well.

[connie-ooi]

@parlough Yeah! I can definitely add it to that page.

[antfitch]

Looks great! Small style changes.

[antfitch]

Let's follow the Google Developer Style guide for procedures: https://developers.google.com/style/procedures

If you have any questions, ping me!

[antfitch]

Love it!