- Joined
- Mar 28, 2007
- Messages
- 2,490 (0.39/day)
- Location
- Your house.
System Name | Jupiter-2 |
---|---|
Processor | Intel i3-6100 |
Motherboard | H170I-PLUS D3 |
Cooling | Stock |
Memory | 8GB Mushkin DDR3L-1600 |
Video Card(s) | EVGA GTX 1050ti |
Storage | 512GB Corsair SSD |
Display(s) | BENQ 24in |
Case | Lian Li PC-Q01B Mini ITX |
Audio Device(s) | Onboard |
Power Supply | Corsair 450W |
Mouse | Logitech Trackball |
Keyboard | Custom bamboo job |
Software | Win 10 Pro |
Benchmark Scores | Finished Super PI on legendary mode in only 13 hours. |
You have to understand how programs work to understand that multi-core, most of the time, is not a good thing. It adds many layers of complexity which a single, faster core gets the same performance with pure simplicity on the coding end.
Simply put, if you got a nail and you need to hammer it in, would you rather have one really big hammer or 48 tiny hammers?
There's a few occassions where multiple cores are good but, those few times are exactly that, a few (no more than four). Faster cores are preferred over SMT.
Irrelevant -- like I said, there's an upper limit to how fast a single-core can go, therefore multi-core is the only way.
Unless you think you'll be happy with 4GHz 10 years from now.