chore: update next.js submodule with TaskChannels optimization

[xusd320]

Sync perf optimization from vercel/next.js#86266:

• Pre-allocate TaskChannels to avoid HashMap lookups during send/recv
• Make worker_pool take priority when both features are enabled

Depends on: utooland/next.js#101

[gemini-code-assist]

Summary of Changes

Hello @xusd320, 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 updates the next.js submodule to integrate a significant performance optimization. The core of this enhancement involves refining how TaskChannels are managed to minimize lookup overhead during communication and prioritizing worker_pool operations under specific conditions. This change aims to improve the overall efficiency and responsiveness of the Next.js application.

Highlights

• Next.js Submodule Update: The next.js submodule has been updated to a newer commit (54dabf58ac5c254d0bab981614ba59f6604f6635), incorporating recent performance optimizations.
• TaskChannels Optimization: This update includes a performance enhancement that pre-allocates TaskChannels to reduce HashMap lookups during send/receive operations, improving efficiency.
• Worker Pool Priority: The updated submodule also ensures that the worker_pool takes priority when both TaskChannels and worker_pool features are enabled, optimizing resource allocation.

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 next.js submodule to a new commit. The goal is to sync performance optimizations from the upstream repository, specifically pre-allocating TaskChannels and prioritizing the worker_pool feature. The change is a straightforward submodule pointer update and aligns with the description. As there are no direct code changes in this repository, only the submodule hash update, there are no specific code review comments to provide.