sech1, gingeropolous, maybe more pools will turn on self-select when I get round to implementing in nodejs-pool for them.

I started this last week, just not had time to finish (due to vomiting over JS).

There's also a couple of forks of nodejs-pool and the required packages (like node-cryptoforknote-util et al)

If I/we could talk say supportxmr into switching it on if I implement, that would be a first big pool with it implemneted.

Others might follow.

Do you see any regular pattern (i.e. wave) on the first image here: minexmr.com/pools.html?

cohcho waves are daily cycles. Either botnets or hobby miners who turn off PC for the night.

Do you have updated plot of `nonce.txt` for this hardfork?

Does this patch to bc_dyn_stats in monerod will show the same hashrate as your script for N recent blocks: paste.debian.net/plainh/893a5ec8?

It should, formula is the same

`bc_dyn_stats 440` says Height: 1981278, 842.52MH/s with that patch

Looks like randomx library has been loaded into memory from buffer successfuly. 5 days doesn't sound like a reasonable amount of time but anyway it's done.

Almost, almost: en.wikichip.org/wiki/hisilicon/kunpeng/920-6426

Only L3 cache is not enough

Each core is custom design based on Cortex-A72, it should be pretty efficient on RandomX

yeah, most ARM designs are still light on cache

Phytium still seems to be the only design that has adequate cache per core

But Kunpeng is almost there, it has everything. It can mine Wownero already at full potential

Give it a couple of years and we'll see server and desktop ARM CPUs with 2 MB cache per core

It even has 8 memory channels

My rough estimate is it should be able to do 450 h/s per thread, 14.4 kh/s with 32 threads

at 180 W TDP, 80 h/s per watt

maybe less than 180 W because only half of the cores are used

What way did you find this link? (It has been posted here already several times)

80 h/s os on par for 3900x

is*

1 GH/s incoming

according to your algo?

.network

XMR network hashrate 60 : 1,032.329 MH/s

last 60 blocks

fortunero.net tests winner at 191313 and it was ~800MH/s at that time

height 1981482, bc_dyn_stats 60 says 1.04GH/s here too

There is a growing suspicion that it is your algorithm that is increasing the hashrate, sech1!

Well, there's going to be one more speed boost for old Xeons/Opterons

I just need to test it to get numbers

1918313*

1981313?

how old?

the E5 got a decent jump from 5.0.1 -> 5.1

Westmere, Sandy Bridge, IviBridge

so v1, v2 Xeons and older

v3 and newer won't get big speedup

but they'll also get small 1% speedup

fixed type in fortunero.net related sentence

yes, you fixed but still got the number wrong :D

yes, 8 and 1 should be swapped

oooh, old opterons get a boost!?!?!?!

time to turn on those banshees