React Context vs. Redux Toolkit: When does state complexity demand Redux?

You're hitting the right spot by asking this! The practical benchmarks or 'red flags' indicating it's time to consider Redux Toolkit usually revolve around these points:

1. **Performance Issues from Re-renders:** If changes to a small part of your global Context value are causing widespread, unnecessary re-renders across many components, impacting performance. Redux Toolkit with React Redux's optimized selectors helps prevent this.
2. **Debugging Complexity:** When tracing state changes, understanding the flow of data, or reproducing state-related bugs becomes a significant headache. Redux DevTools offer invaluable time-travel debugging and action logs.
3. **Intricate Asynchronous Logic:** If you're struggling to manage complex sequences of API calls, optimistic updates, or interdependent async operations with `useEffect` and `useReducer` alone. RTK Query or Redux Thunks/Sagas simplify this greatly.
4. **Predictability and Traceability:** When your global state updates start feeling chaotic, and you lack a clear, centralized history of actions and state transitions. Redux provides a highly predictable state container.
5. **Scaling and Team Collaboration:** For very large applications or growing teams, Redux Toolkit offers a more opinionated, structured, and consistent pattern for state management that improves maintainability and onboarding.

You're asking a great question that many React developers face. The primary indicators that it's time to consider Redux Toolkit over Context API + useReducer often revolve around three main areas: performance, debugging, and complexity of state interactions.

1. **Performance Issues from Re-renders:** If you're experiencing noticeable performance degradation due to many components re-rendering unnecessarily when only a small part of your global context state changes, Redux Toolkit's optimized selectors can provide much more granular control over component updates, preventing unnecessary re-renders.
2. **Debugging and Traceability:** When tracing state changes becomes a significant challenge, especially with asynchronous operations or complex interactions. Redux DevTools offer unparalleled visibility into state changes, action history, and even time-travel debugging, which is a game-changer for complex applications.
3. **Complex Asynchronous Logic and Side Effects:** If your `useReducer` dispatch logic is becoming bloated with intricate asynchronous operations, network requests, or interactions with multiple parts of your application state, Redux Toolkit's structured approach with Redux Thunk (built-in) or RTK Query provides a much cleaner and more maintainable way to handle these side effects.
4. **Deeply Nested Global State and Cross-Cutting Concerns:** When a significant portion of your application needs access to the same, often deeply nested, global state, and modifications to one part of that state frequently impact other, seemingly unrelated parts. Redux Toolkit encourages a more centralized and predictable state structure.
5. **Team Collaboration and Scalability:** For larger teams and applications, Redux Toolkit's opinionated structure and conventions can enforce consistency, making it easier for new developers to understand the state flow and contribute effectively without introducing unexpected side effects.

Essentially, if you find yourself spending more time debugging state-related re-renders, struggling to trace state changes, or wrestling with complex async logic within your `useReducer` pattern, those are strong signals that Redux Toolkit could offer a more robust and maintainable solution.