docs: update benchmarks and changelog

[but212]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @but212, 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 focuses on maintaining up-to-date project documentation. It updates the performance benchmark results to reflect the current state of the atom-effect library and cleans up the changelog by removing obsolete entries and clarifying existing ones. This ensures that users and contributors have access to the most accurate information regarding the library's performance characteristics and historical changes.

Highlights

• Benchmark Documentation Updates: The performance benchmark documentation has been updated to reflect the latest metrics for various operations, including Atom reads, Computed recomputations, and real-world application scenarios. This ensures that the reported performance figures are current and accurate.
• Changelog Refinement: The CHANGELOG.md file has been refined by removing outdated performance optimization entries (V8 Optimization and Notification Loop) and clarifying the description for the subscriber pool removal to accurately state its primary benefit as memory usage reduction. The 'Performance' section was also renamed to 'Changed'.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 updates the project's documentation, specifically the changelog and benchmark results. The changes to CHANGELOG.md align the 'Unreleased' section with the document's formatting standards and adjust performance claims to accurately reflect the latest benchmark data. The benchmark files (BENCHMARKS.md and BENCHMARKS_DETAILED.md) have been updated with new metrics, and the summary data is consistent with the detailed results. The removal of specific hardware details like CPU cores from the benchmark environment makes the description more robust. Overall, these changes improve the accuracy and consistency of the documentation. The pull request is well-structured and ready to be merged.