Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

vercel / next.js Public

Notifications You must be signed in to change notification settings
Fork 27.1k
Star 128k

Code
Issues 3k
Pull requests 569
Discussions
Actions
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Security
Insights

[Turbopack] use thread local trace collecting#73615

Merged

sokra merged 4 commits intocanaryvercel/next.js:canaryfrom sokra/perf-tracing-2vercel/next.js:sokra/perf-tracing-2Copy head branch name to clipboard

Dec 10, 2024

+573-231

Conversation Commits4 (4)Checks Files changed

Commits

Commits on Dec 9, 2024

use thread local trace collecting
sokra
committed
assign globally unique ids to spans, handle out of order trace files
sokra
committed
use thread local buffering with stealing for better performance
sokra
committed
clippy
sokra
committed

Footer

© 2024 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.