Standardize the Order of Shared Performance Panels Between Eevee and Cycles

While Cycles and Eevee are fundamentally different rendering engines, they share several performance-related settings such as Memory, Viewport, and Compositor. However, these panels are currently presented in a different order between the two engines. For example, in Eevee, the order under the Performance section is:

Memory

Viewport

Compositor

Whereas in Cycles, the order is:

Compositor

...

Memory

...

Viewport

This inconsistency can interrupt workflow efficiency, especially for users who frequently switch between the two engines. It creates unnecessary friction when trying to locate familiar settings, even though the panels themselves are functionally similar or identical.

Proposal: Unify the layout and order of shared performance-related panels (such as Memory, Viewport, and Compositor) between Eevee and Cycles. Whether the layout follows Cycles or Eevee does not matter as much as maintaining consistency across both engines. This will improve usability, reduce cognitive load, and make the UI more predictable when switching render engines.

Benefits:

Streamlined user experience

Easier onboarding for new users

Less time spent searching for the same settings in different engines

Improved interface consistency and polish

Thank you for considering this suggestion!