A lengthy task in a resource-intensive application.

[veksa]

I have a highly-loaded SPA application with frequent store updates and, consequently, a high frequency of interface updates. Calculating data takes a significant amount of time, resulting in a long task of around 70ms. Additionally, due to changes in the pull request - #26512, a microtask is executed with an update, also taking a considerable amount of time.

The total task execution time is 117ms. For me, it would be better to move flushSyncCallbacks into a separate task rather than running it as a microtask.

Is it possible to provide control over scheduling processing? For instance, allowing the replacement of the use of queueMicrotask with something custom, perhaps as a parameter in createRoot, or similar to what is done in react-redux (https://github.com/reduxjs/react-redux/blob/master/src/utils/batch.ts).

I have some ideas for implementation and can create a pull request.

React version: 18.2.0

The current behavior

A long task in conjunction with a microtask.

The expected behavior

The code executed in a microtask runs in a separate task.

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

[github-actions]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you!