Hacker News new | ask | show | jobs
by Scramblejams 2927 days ago
I've never trusted hyperthreading for workloads I haven't tested. Sometimes it's faster, often it's slower. Beyond that, I've been suspicious of its security implications from day one. My first trip through the BIOS on a personal machine always includes turning it off.
2 comments

Can you give example of where it was slower for you with HT enabled?
Running finite element models with MSC NASTRAN, basically heavy matrix math. Matrices were NxN, N was around 10 million. This was on a server with 36 cores and a half terabyte of RAM, purchased in 2014.

Also seen Erlang workloads where you could get a bit of throughput increase with your VM scheduler scheduling more threads than your physical cores (so starting to use HT) but the latency would spike and become very unpredictable, which was a bad tradeoff for the use case.

HPC workloads normally at least won't benefit and probably take a hit from HT on Xeon-ish hardware at least. It's normally turned off on HPC compute nodes (perhaps in software so the resource manager can enable per-job if necessary). There are exceptions, particularly with KNC and, perhaps, KNL. The situation is likely different for POWER, but I don't have experience of it.
You could just buy i5 based machines instead which don't have hyperthreading.
From what I have seen, I think many dual-core i5 CPUs for notebooks support hyperthreading.
The U (ultra-low power) lines are indeed two-core with Hyperthreading. All others are 4 core without.
Okay, that explains it. The only i5-based systems I have used (or still use) are notebooks.
Yes, you're right, I was thinking only about desktop CPUs, forgetting the laptop CPUs are different.