- Joined
- Feb 20, 2019
- Messages
- 8,344 (3.90/day)
System Name | Bragging Rights |
---|---|
Processor | Atom Z3735F 1.33GHz |
Motherboard | It has no markings but it's green |
Cooling | No, it's a 2.2W processor |
Memory | 2GB DDR3L-1333 |
Video Card(s) | Gen7 Intel HD (4EU @ 311MHz) |
Storage | 32GB eMMC and 128GB Sandisk Extreme U3 |
Display(s) | 10" IPS 1280x800 60Hz |
Case | Veddha T2 |
Audio Device(s) | Apparently, yes |
Power Supply | Samsung 18W 5V fast-charger |
Mouse | MX Anywhere 2 |
Keyboard | Logitech MX Keys (not Cherry MX at all) |
VR HMD | Samsung Oddyssey, not that I'd plug it into this though.... |
Software | W10 21H1, barely |
Benchmark Scores | I once clocked a Celeron-300A to 564MHz on an Abit BE6 and it scored over 9000. |
That's a good point.Back to the technicalities... (if you're not interested, skip this post)
The review says the Navi 32 GPU has 4 shader arrays. That brings us to 960 shaders, or 15 CUs per array. Considering that CUs come in pairs with RDNA 3, this doesn't compute.
However, according to an article on wccftech.com, the GPU has 3 shader arrays, which means 20 CUs per array, that is 1280 shaders per array.
@W1zzard - Not that it matters much, I just thought I'd bring this to your attention. Great review anyway, as always!
One way it could be true is even each shader array actually has 16CUs in it and AMD are disabling some for yield reasons.
I've already questioned the 60CU in prior posts leading up to launch, the obvious number to fit the RDNA3 family was 64CU...