newtekie1
Semi-Retired Folder
- Joined
- Nov 22, 2005
- Messages
- 28,472 (4.23/day)
- Location
- Indiana, USA
Processor | Intel Core i7 10850K@5.2GHz |
---|---|
Motherboard | AsRock Z470 Taichi |
Cooling | Corsair H115i Pro w/ Noctua NF-A14 Fans |
Memory | 32GB DDR4-3600 |
Video Card(s) | RTX 2070 Super |
Storage | 500GB SX8200 Pro + 8TB with 1TB SSD Cache |
Display(s) | Acer Nitro VG280K 4K 28" |
Case | Fractal Design Define S |
Audio Device(s) | Onboard is good enough for me |
Power Supply | eVGA SuperNOVA 1000w G3 |
Software | Windows 10 Pro x64 |
Worth noting: Under some (most?) circumstances that's only true for LAN-WAN and WAN-LAN traffic. Most routers (all newer ones should) avoid running traffic through the CPU as much as possible. WAN-LAN and vice versa necessitates CPU use (NAT, Routing table lookup) in all but the big-boy routers in top end commercial hardware (and probably even in that hardware, too). LAN-LAN traffic can be handled by the inbuilt switch. How sophisticated and seperated the switch hardware from CPU is in a consumer router, is another matter. (If at all, depending on architecture... see the PDF I linked)
Yes, I was talking LAN-WAN/WAN-LAN traffic. Straight LAN-LAN traffic is handled by the switch and doesn't really touch the router's CPU.