dice.camp is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon server for RPG folks to hang out and talk. Not owned by a billionaire.

Administered by:

Server stats:

1.6K
active users

#turbostat

0 posts0 participants0 posts today

#Turbostat Utility Bumps 1024 #CPU Core Limit To 8192 Cores After #HPE Breaches It With a 1152 Core unnamed system.
We currently aren't aware of any server CPU configurations that can exceed this limit (in terms of physical cores), so this may be a custom or next-generation solution from #Intel or #AMD. The utility currently only supports #x86 processors, which seemingly rules out an Arm system from causing the issue.
phoronix.com/news/Linux-6.15-T

www.phoronix.comTurbostat Utility Bumps 1024 CPU Core Limit To 8192 Cores After HPE Breaches It With 1152 Cores
Continued thread

another example (Newton-Raphson zooming for Mandelbrot set):

with 7 threads : 105.26 Watts * 12.2 seconds = 1284.6 Joules
with 1 thread : 54.17 Watts * 52.1 seconds = 2822.3 Joules
sleeping / idle overhead : 26.01 Watts
7 threads minus overhead (105 - 26.01)W * 12.2s = 964 Joules
1 thread minus overhead (54.17 - 26.01)W * 52.1s = 1467.2 Joules
if the machine would be on/idle anyway: 105.26W * 12.2s + 26.01 W * (52.1 - 12.2)s = 2321.9 Joules

thus using more threads saves energy even when parallelism efficiency is far from perfect: best to get in/out as quickly as possible so you can turn the machine off (ideal case) / leave it fully idle (second best)

power consumption doesn't scale linearly with load (a little load increases a lot vs baseline: 1 thread doubles idle power consumption, but high load doesn't increase much more: 7 threads quadruples idle power consumption)

measured with turbostat on Debian, AMD 2700X CPU with default CPU scaling governor, usual browser/email/etc running too