Re: cpu temperature readings

[Robert Elz <kre%munnari.OZ.AU@localhost>]

    Date:        Thu, 29 Jun 2023 08:27:05 -0000 (UTC)
    From:        mlelstv%serpens.de@localhost (Michael van Elst)
    Message-ID:  <u7jf8o$e62$1%serpens.de@localhost>

  | You could run a benchmark like 'openssl speed sha256' and compare
  | the 3400 MHz target and the target and step lower.

First, my userland (that I run most of the time anyway) hasn't been
updated since the system was installed, just the kernel, and occasional
binaries that need it, so this is an oldish openssl, but I doubt that
that matters for this purpose, it is the same binary in all tests.
I "primed the cache" by running it once before these tests started,
so they should all have a similar starting point.   I made the cpu
frequency adjustments from another window (where I have a root shell).

At 3400:

jacaranda$ openssl speed sha256
Doing sha256 for 3s on 16 size blocks: 8539390 sha256's in 2.99s
Doing sha256 for 3s on 64 size blocks: 4782823 sha256's in 2.98s
Doing sha256 for 3s on 256 size blocks: 1926335 sha256's in 2.98s
Doing sha256 for 3s on 1024 size blocks: 554719 sha256's in 3.00s
Doing sha256 for 3s on 8192 size blocks: 84392 sha256's in 2.89s
Doing sha256 for 3s on 16384 size blocks: 40283 sha256's in 2.97s
OpenSSL 1.1.1n  15 Mar 2022
NetBSD 9.99.97
options:bn(64,64) rc4(16x,int) des(int) aes(partial) idea(int) blowfish(ptr) 
gcc version 10.3.0 (NetBSD nb1 20210411) 
The 'numbers' are in 1000s of bytes per second processed.
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes  16384 bytes
sha256           45741.63k   102821.86k   165372.82k   189407.22k   238969.67k   222146.30k

At 3200 (next lower than 3400)

jacaranda$ openssl speed sha256
Doing sha256 for 3s on 16 size blocks: 7979827 sha256's in 2.99s
Doing sha256 for 3s on 64 size blocks: 3945995 sha256's in 2.99s
Doing sha256 for 3s on 256 size blocks: 1634539 sha256's in 3.00s
Doing sha256 for 3s on 1024 size blocks: 491637 sha256's in 3.00s
Doing sha256 for 3s on 8192 size blocks: 65334 sha256's in 3.00s
Doing sha256 for 3s on 16384 size blocks: 36043 sha256's in 3.00s
OpenSSL 1.1.1n  15 Mar 2022
NetBSD 9.99.97
options:bn(64,64) rc4(16x,int) des(int) aes(partial) idea(int) blowfish(ptr) 
gcc version 10.3.0 (NetBSD nb1 20210411) 
The 'numbers' are in 1000s of bytes per second processed.
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes  16384 bytes
sha256           42715.70k    84434.53k   139480.66k   167812.10k   178405.38k   196908.47k


At 1700 (not the next lower step, but one where the relationship
should be easier to detect)

jacaranda$ openssl speed sha256
Doing sha256 for 3s on 16 size blocks: 4367949 sha256's in 2.98s
Doing sha256 for 3s on 64 size blocks: 2252212 sha256's in 2.90s
Doing sha256 for 3s on 256 size blocks: 970476 sha256's in 2.91s
Doing sha256 for 3s on 1024 size blocks: 295952 sha256's in 2.92s
Doing sha256 for 3s on 8192 size blocks: 44675 sha256's in 2.98s
Doing sha256 for 3s on 16384 size blocks: 18225 sha256's in 2.91s
OpenSSL 1.1.1n  15 Mar 2022
NetBSD 9.99.97
options:bn(64,64) rc4(16x,int) des(int) aes(partial) idea(int) blowfish(ptr) 
gcc version 10.3.0 (NetBSD nb1 20210411) 
The 'numbers' are in 1000s of bytes per second processed.
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes  16384 bytes
sha256           23452.08k    49618.44k    85433.93k   103892.65k   122728.91k   102470.28k

At 800 (also not the next lower, 850 isn't an available frequency)

jacaranda$ openssl speed sha256
Doing sha256 for 3s on 16 size blocks: 2186921 sha256's in 2.99s
Doing sha256 for 3s on 64 size blocks: 1100432 sha256's in 3.00s
Doing sha256 for 3s on 256 size blocks: 454525 sha256's in 2.99s
Doing sha256 for 3s on 1024 size blocks: 122616 sha256's in 3.00s
Doing sha256 for 3s on 8192 size blocks: 16505 sha256's in 3.00s
Doing sha256 for 3s on 16384 size blocks: 11058 sha256's in 2.98s
OpenSSL 1.1.1n  15 Mar 2022
NetBSD 9.99.97
options:bn(64,64) rc4(16x,int) des(int) aes(partial) idea(int) blowfish(ptr) 
gcc version 10.3.0 (NetBSD nb1 20210411) 
The 'numbers' are in 1000s of bytes per second processed.
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes  16384 bytes
sha256           11686.95k    23499.38k    38863.86k    41894.82k    45129.83k    60735.59k

And then for fun, at 3401 ... this one I needed to run the test several
times until the kernel picked one of the fastest processors to run it on
(for the others it shouldn't make any difference, any of them should be
able to run at 3400 or below, though I am not sure if the economy processors
actually do, at non-turbo speeds that might be limited to 2500GHz, though
cpuctl claims they run at 3400 - it does get their max turbo speed right)

jacaranda$ openssl speed sha256
Doing sha256 for 3s on 16 size blocks: 15927310 sha256's in 2.99s
Doing sha256 for 3s on 64 size blocks: 8587518 sha256's in 3.00s
Doing sha256 for 3s on 256 size blocks: 2803948 sha256's in 3.00s
Doing sha256 for 3s on 1024 size blocks: 614484 sha256's in 3.00s
Doing sha256 for 3s on 8192 size blocks: 94334 sha256's in 3.00s
Doing sha256 for 3s on 16384 size blocks: 51603 sha256's in 3.00s
OpenSSL 1.1.1n  15 Mar 2022
NetBSD 9.99.97
options:bn(64,64) rc4(16x,int) des(int) aes(partial) idea(int) blowfish(ptr) 
gcc version 10.3.0 (NetBSD nb1 20210411) 
The 'numbers' are in 1000s of bytes per second processed.
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes  16384 bytes
sha256           85258.27k   183444.98k   239350.01k   209813.81k   257594.71k   281821.18k

That should, if it ran as fast as possible, be almost twice as fast
as a run at 2800, so here's that one:

jacaranda$ openssl speed sha256
Doing sha256 for 3s on 16 size blocks: 8331596 sha256's in 3.00s
Doing sha256 for 3s on 64 size blocks: 3563594 sha256's in 3.00s
Doing sha256 for 3s on 256 size blocks: 1534171 sha256's in 3.00s
Doing sha256 for 3s on 1024 size blocks: 433536 sha256's in 2.99s
Doing sha256 for 3s on 8192 size blocks: 59305 sha256's in 2.99s
Doing sha256 for 3s on 16384 size blocks: 28675 sha256's in 3.00s
OpenSSL 1.1.1n  15 Mar 2022
NetBSD 9.99.97
options:bn(64,64) rc4(16x,int) des(int) aes(partial) idea(int) blowfish(ptr) 
gcc version 10.3.0 (NetBSD nb1 20210411) 
The 'numbers' are in 1000s of bytes per second processed.
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes  16384 bytes
sha256           44479.66k    76124.84k   131003.26k   148276.84k   162375.19k   156760.49k

And it should be more than twice as fast as a run at 2700.   So here's
that one.

jacaranda$ openssl speed sha256
Doing sha256 for 3s on 16 size blocks: 7751675 sha256's in 3.00s
Doing sha256 for 3s on 64 size blocks: 3858292 sha256's in 3.00s
Doing sha256 for 3s on 256 size blocks: 1419658 sha256's in 3.00s
Doing sha256 for 3s on 1024 size blocks: 493049 sha256's in 3.00s
Doing sha256 for 3s on 8192 size blocks: 59434 sha256's in 3.00s
Doing sha256 for 3s on 16384 size blocks: 29193 sha256's in 3.00s
OpenSSL 1.1.1n  15 Mar 2022
NetBSD 9.99.97
options:bn(64,64) rc4(16x,int) des(int) aes(partial) idea(int) blowfish(ptr) 
gcc version 10.3.0 (NetBSD nb1 20210411) 
The 'numbers' are in 1000s of bytes per second processed.
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes  16384 bytes
sha256           41411.29k    82337.68k   121265.41k   168350.18k   162348.56k   159432.70k

It looks to me as if the frequency adjustments are working properly,
though NetBSD's cpu selection algorithm doesn't (yet anyway) really
understand processors like this.

kre