Were there any tools you used to help you with this or did you just look at your build directly?
Are you saying that the AMD stuff doesn't do hyperthreading?
Re:Linus Torvalds has switched to AMD
by 411111111111111 on Monday May 25, 2020 @02:01AM
(#23298366)
... Considering hyperthreading is a proprietary Intel system: no, AMD doesn't do it.
Not sure how that would be in any way relevant to the parents point though.
It should be noted that AMD has SMT, which is pretty much the same thing.
While shoring up nomenclature: I believe “simultaneous multi-threading” (SMT) is the generic term and “Hyperthreading” is Intel’s branding of their SMT implementation.
Calling AMD’s SMT “hyperthreading” is like calling all tissues Kleenex. It’s fine imo, but it doesn’t hurt to know these things.
Re:Linus Torvalds has switched to AMD
by NotSammyHagar on Monday May 25, 2020 @03:40AM
(#23298924)
No, they were almost certainly talking about some part of their build process limited it to a few processes (like maybe a 'make -k 6' limitation), or something that could be easily parallelized.
Re:Linus Torvalds has switched to AMD
by Someone1234 on Monday May 25, 2020 @08:22AM
(#23300254)
It was worse than even that, several parts of the build process were fully sequential. I only got benefit of multiple cores at all because the tooling in those sequential steps were utilizing it, or related system services were.
But, yes, I also did change at least one config to allow it to spawn more than 2 threads.
Re:Linus Torvalds has switched to AMD
by chriswitts on Monday May 25, 2020 @03:13AM
(#23298783)
AMD calls it SMT (Simultaneous MultiThreading).
Re:Linus Torvalds has switched to AMD
by ralls_ebfe on Monday May 25, 2020 @03:48AM
(#23298973)
Simultanous Multithreading is the actual term. Hyperthreading is just Intel SMT in marketing language.
Re:Linus Torvalds has switched to AMD
by littlecranky67 on Monday May 25, 2020 @02:45PM
(#23303653)
Yepp, SMT is the generic term also used in academia for ages. Source: Old editions of venerable "Computer Architecture" by Hennessy & Patterson.
When I first starting using the new CPU the most striking thing was how /few/ of the cores were under-load during my compilations due to several bottlenecks in my build I didn't realize I had. Over half of my cores were near idle.
I was able to reduce compilation times by 75% (126~ sec to under 31~ sec), just by allowing several processes to run concurrently, and changing the order of a few others, so they weren't fighting over file system locks.
I went back and tested it on the old i7 machine, and still got a 30%~ improvement. My point is: Upgrade away, but make sure your tooling and scripts are designed for that type of concurrency otherwise you'll be wasting a lot of the potential. Mine weren't.