This looks like an interesting rabbit hole to go down for a bit :-)
-
-
Replying to @sigfpe @Augustsson
AVX-512 will also easily throttle your cpu clock. So uh, maybe not the best idea in an inner loop, so check it doesn't.
1 reply 0 retweets 1 like -
Replying to @PLT_cheater @Augustsson
I usually forget about power so that's interesting!
1 reply 0 retweets 0 likes -
Replying to @sigfpe @Augustsson
My guess is it's less about power and more about having to reconfigure parts of the pipeline, or uh, something like that. Basically part of the cpu is io bound because an earlier part is cpu bound. Solution: clock down everything except the lagging part. (My guess)
1 reply 0 retweets 0 likes -
This article talks about avx slowdowns: https://blog.cloudflare.com/on-the-dangers-of-intels-frequency-scaling/ …
1 reply 0 retweets 0 likes -
I wonder if
@johnmdanskin,@jangray,@TimSweeneyEpic, or@ID_AA_Carmack have insight as to why AVX induces freq scaling. I would love to know what is behind this. This CERN pdf points to power limits, but it too seems to be a guess rather than knowledge. https://indico.cern.ch/event/327306/contributions/760669/attachments/635800/875267/HaswellConundrum.pdf …2 replies 0 retweets 0 likes -
Replying to @PLT_cheater @sigfpe and
(Wondering if any of you know (of) each other -
@sigfpe has done some really good work in 3D graphics)1 reply 0 retweets 0 likes -
Replying to @PLT_cheater @sigfpe and
I think AVX512 downclocking is a temporary artifact that can be improved in future architectures with finer thermal management granularity in time and space.
2 replies 0 retweets 1 like -
Replying to @TimSweeneyEpic @PLT_cheater and
I’d expect keeping it running at full capacity for a long time would necessarily cause thermal limiting. However, occasional burst use ought not slow down the chip for a much longer duration than it’s used. Overall I’m very happy to have AVX512 as a step towards convergence.
1 reply 0 retweets 0 likes -
CPU=GPU through many cores and wide vector units.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.