From the PS5 new 1100 model hands-on from Digital Foundry we learn interesting power consumption measures.
- Control regular gameplay (30fps RT mode): 170W
- Most demanding scene (corridor of death, 30fps RT mode), but still gameplay: 200W
- Photo mode unlocked (non gameplay, taxes mainly the GPU according to a reliable source who has actually profiled the game during photo-mode): 214W.
So what does it tell us if we trust Cerny and the dynamic clock system that is based on instructions load which are themselves based on actual power draw? It means the PS5 should run at max clocks in the vast majority of time as it seems the actual max power consumption (so logically the max number of instructions before a downclock) could be higher than 210W (and not 200W like previously thought).
During normal and demanding gameplay the system should run at max CPU / GPU clocks and it could lower the clocks only in very specific conditions: photo modes which are similar as cutscenes / when game is put in the background. All those scenes share the fact that the GPU is not limited by any CPU logic and is stupidly (and uselessly) trying to work as much as it can. It can also happens in plenty of games when you enter the dashboard while a game is running in the background. Also in some games menu and maps.
- Control regular gameplay (30fps RT mode): 170W
- Most demanding scene (corridor of death, 30fps RT mode), but still gameplay: 200W
- Photo mode unlocked (non gameplay, taxes mainly the GPU according to a reliable source who has actually profiled the game during photo-mode): 214W.
So what does it tell us if we trust Cerny and the dynamic clock system that is based on instructions load which are themselves based on actual power draw? It means the PS5 should run at max clocks in the vast majority of time as it seems the actual max power consumption (so logically the max number of instructions before a downclock) could be higher than 210W (and not 200W like previously thought).
During normal and demanding gameplay the system should run at max CPU / GPU clocks and it could lower the clocks only in very specific conditions: photo modes which are similar as cutscenes / when game is put in the background. All those scenes share the fact that the GPU is not limited by any CPU logic and is stupidly (and uselessly) trying to work as much as it can. It can also happens in plenty of games when you enter the dashboard while a game is running in the background. Also in some games menu and maps.