- Joined
- Jan 27, 2015
- Messages
- 1,665 (0.48/day)
System Name | Legion |
---|---|
Processor | i7-12700KF |
Motherboard | Asus Z690-Plus TUF Gaming WiFi D5 |
Cooling | Arctic Liquid Freezer 2 240mm AIO |
Memory | PNY MAKO DDR5-6000 C36-36-36-76 |
Video Card(s) | PowerColor Hellhound 6700 XT 12GB |
Storage | WD SN770 512GB m.2, Samsung 980 Pro m.2 2TB |
Display(s) | Acer K272HUL 1440p / 34" MSI MAG341CQ 3440x1440 |
Case | Montech Air X |
Power Supply | Corsair CX750M |
Mouse | Logitech MX Anywhere 25 |
Keyboard | Logitech MX Keys |
Software | Lots |
I don't think you are going to see big frequency bumps on Zen 5 as you increase power.
AMD and Intel traditionally design for higher clocks, they are 4 (Zen) and 1+3 (Intel) wide decode pipelines.
Apple by comparison was at 7 wide with the A11/A12 and 8 wide back with the A14, and I believe still at 8 with M1. Samsung was at 6 a couple of years ago and generic ARM Cortex was 6. These are all designed to offer optimum performance per clock, but absolute performance is limited by lower clock speeds.
So AMD has now gone with very wide decode pipeline, 8 wide, which barring any big breakthrough in design is going to limit frequency but will get more done per clock.
This is a huge change for them. This is probably a really good, efficient design for a server. It may play out very well in the mobile / laptop space as well.
However, the way I see it, it's going to have some inherent weaknesses in the performance oriented desktop space.
AMD and Intel traditionally design for higher clocks, they are 4 (Zen) and 1+3 (Intel) wide decode pipelines.
Apple by comparison was at 7 wide with the A11/A12 and 8 wide back with the A14, and I believe still at 8 with M1. Samsung was at 6 a couple of years ago and generic ARM Cortex was 6. These are all designed to offer optimum performance per clock, but absolute performance is limited by lower clock speeds.
So AMD has now gone with very wide decode pipeline, 8 wide, which barring any big breakthrough in design is going to limit frequency but will get more done per clock.
This is a huge change for them. This is probably a really good, efficient design for a server. It may play out very well in the mobile / laptop space as well.
However, the way I see it, it's going to have some inherent weaknesses in the performance oriented desktop space.