Aquinus
Resident Wat-man
- Joined
- Jan 28, 2012
- Messages
- 13,153 (2.87/day)
- Location
- Concord, NH, USA
System Name | Apollo |
---|---|
Processor | Intel Core i9 9880H |
Motherboard | Some proprietary Apple thing. |
Memory | 64GB DDR4-2667 |
Video Card(s) | AMD Radeon Pro 5600M, 8GB HBM2 |
Storage | 1TB Apple NVMe, 4TB External |
Display(s) | Laptop @ 3072x1920 + 2x LG 5k Ultrafine TB3 displays |
Case | MacBook Pro (16", 2019) |
Audio Device(s) | AirPods Pro, Sennheiser HD 380s w/ FIIO Alpen 2, or Logitech 2.1 Speakers |
Power Supply | 96w Power Adapter |
Mouse | Logitech MX Master 3 |
Keyboard | Logitech G915, GL Clicky |
Software | MacOS 12.1 |
http://www.intel.com/content/dam/ww...h-gen-core-family-desktop-vol-1-datasheet.pdf
Page 27:
You were saying?
![]()
GB = Gigabytes
Gb = Gigabits
1GB = 8Gb
Do you know why that is? There are 8 bits in a byte.
![Slap :slap: :slap:](https://tpucdn.com/forums/data/assets/smilies/slap-v1.gif)
2GB/s = 16Gb/s which is really just 20Gb/s with 8b/10b encoding overhead like PCI-E has. So no, I'm right in the sense that there are 20Gbps links that can go that speeds in both directions simultaneously. So even if after encoding you factor everything in, you still have to do a ton of saturate it. Once again, stop with the lying. It doesn't do your argument justice.
Stop trying to act like you know something when you don't, before you hurt your trolling finger.