Computing Performance vs Power Consumption
Use event-driven and variable-performance computing architectures so peak processing capability does not drive continuous power system sizing.
CyberTRIZ analysis · Space contradiction TSI001 · one of 8,235 worked contradictions published by CyberTRIZ.AI
Business Context
Advanced spacecraft increasingly require high-performance onboard computing for autonomous navigation, payload processing, artificial intelligence, image analysis, communications management, and fault detection. Increasing processing capability, however, generally increases electrical demand and heat generation. Expanding the power and thermal systems to support peak computing loads can add mass and reduce resources available to payloads and other mission functions.
Space TRIZ Resolution
Computing resources should operate according to actual workload rather than continuously at maximum performance. Specialized accelerators, low-power processors, event-driven computation, variable processing modes, and selective transfer of non-time-critical workloads to ground infrastructure can reduce average energy consumption. High-performance processing can remain available for demanding tasks without defining the spacecraft’s continuous power requirement.
Applicable TRIZ Principles
Principle 15 – Dynamics adjusts computing performance according to workload and mission conditions.
Principle 19 – Periodic Action activates intensive processing only when required.
Principle 28 – Mechanics Substitution replaces inefficient general-purpose processing with specialized computing architectures where appropriate.
Expected Outcome
Higher onboard computing capability
Lower average power consumption
Reduced thermal load
Improved computing efficiency
Decision Indicators
Early indicators include:
Processor upgrades require substantial power-system expansion.
Computing hardware operates near maximum capability during low-demand periods.
Thermal limits restrict onboard processing.
High-performance processors remain continuously powered despite intermittent workloads.
Ground resources could handle non-time-critical computation but are not used.