e4a5b11b97 [turbo-tasks-backend] Single-item optimization for lost follower operations (#93200)
## What?

Adds performance optimizations for the common case of single-item lost
follower operations in the turbo-tasks-backend aggregation update
system, along with improved tracing capabilities for debugging.

## Why?

When profiling turbopack operations, we observed that many aggregation
update jobs involve only a single upper losing a single follower. The
previous implementation always used vectors and iteration even for these
single-item cases, adding unnecessary allocation overhead.

Additionally, the existing `trace_aggregation_update` feature was
incomplete (compilation errors) and lacked visibility into task data and
operation statistics.

## How?

### Single-item optimization
- Added a dedicated `InnerOfUpperLostFollower` job variant and
`inner_of_upper_lost_follower` function to handle the single upper +
single follower case without vector allocation
- Optimized the plural variants (`InnerOfUppersLostFollowers`,
`InnerOfUppersLostFollower`, `InnerOfUpperLostFollowers`) to delegate to
the singular function when they contain only one item

### Tracing improvements  
- Added `trace_aggregation_update_stats` feature flag that enables
counters for all aggregation update job types (new_followers,
lost_followers, balance_edge, optimize_task, etc.) recorded in trace
spans
- Fixed `trace_aggregation_update` feature compilation errors by using
`task.get_task_description()` instead of
`ctx.get_task_description(task_id)`
- Gated the `TaskDataCategory` used in aggregation update
`ctx.task(...)` calls behind a const that resolves to `Meta` by default
and `All` when tracing is enabled, so traces can see full task data
without affecting default performance

<!-- NEXT_JS_LLM_PR -->

---------

Co-authored-by: Claude Opus 4.5 <[email protected]>
2026-04-28 21:45:43 +02:00
2025-10-13 10:43:51 +02:00
…
…

Next.js logo

Next.js

Vercel logo NPM version License Join the community on GitHub

Getting Started

Used by some of the world's largest companies, Next.js enables you to create full-stack web applications by extending the latest React features, and integrating powerful Rust-based JavaScript tooling for the fastest builds.

Documentation

Visit https://nextjs.org/docs to view the full documentation.

Community

The Next.js community can be found on GitHub Discussions where you can ask questions, voice ideas, and share your projects with other people.

To chat with other community members you can join the Next.js Discord server.

Do note that our Code of Conduct applies to all Next.js community channels. Users are highly encouraged to read and adhere to it to avoid repercussions.

Contributing

Contributions to Next.js are welcome and highly appreciated. However, before you jump right into it, we would like you to review our Contribution Guidelines to make sure you have a smooth experience contributing to Next.js.

Good First Issues:

We have a list of good first issues that contain bugs that have a relatively limited scope. This is a great place for newcomers and beginners alike to get started, gain experience, and get familiar with our contribution process.


Security

If you believe you have found a security vulnerability in Next.js, we encourage you to responsibly disclose this and NOT open a public issue.

To participate in our Open Source Software Bug Bounty program, please email [email protected]. We will add you to the program and provide further instructions for submitting your report.

S
Description
The React Framework
Readme
2.4 GiB
Languages
JavaScript 55.6%
TypeScript 30%
Rust 12.9%
MDX 0.7%
CSS 0.7%