-
-
Notifications
You must be signed in to change notification settings - Fork 666
perf: launch background tasks immediately #10484
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for rspack ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as spam.
This comment was marked as spam.
📝 Benchmark detail: Open
|
CodSpeed Performance ReportMerging #10484 will not alter performanceComparing 🎉 Hooray!
|
f92f4b3
to
649da70
Compare
Summary
Currently the main tasks run in the scheduler thread. If there's a time consuming main task, the scheduler thread will get stuck and doesn't have time to launch the background tasks.
This pr prevents the background tasks from being put into the task queue. Instead, the scheduler launches them as soon as they are returned.
Checklist