-
dukenukem
"The first professional #XMR Miner, pioneering XMR Mining!" -
nitter.net/BITMAINtech/status/1695783295806775605
-
DataHoarder
> Support RISC-V, Available For Mining Multiple Cryptocurrencies
-
DataHoarder
huh? cluster of RISC-V cores?
-
hyc
<interesting, since we never wrote a RISC-V JIT ourselves.
-
hyc
if it's real, it's yet another case of for-profit companies exploiting permissive licenses. free software deves should never use anything but GPL-family licenses
-
DataHoarder
oddly the numbers look almost equal to
tevador/RandomX #31 doing the math
-
DataHoarder
212000 / 1350 ~= 157 vs 15000 / 95 ~= 157.9
-
hyc
that was an upper bound in efficiency at the time. and yet ryzens are alrady at the 150H/J region
-
sech1
212 kh? So I was right, it's those units that were mining since December 2021
-
hyc
which means this thing isn't any more efficient than current CPUs, so...
-
sech1
And power efficiency is not even impressive
-
sech1
-
sech1
those horizontal lines we've noticed after Christmas 2021 and in early 2022
-
hyc
ah right
-
sech1
so they're dumping 2 year old devices :D
-
sech1
2 years of "testing" :D
-
hyc
so they've been at it for at least 2 years, and all they could come up with is barely at parity with AMD
-
sech1
well, 2 years ago they were a bit ahead of best CPUs
-
sech1
now it's on par with tuned Zen4 CPUs
-
sech1
Zen4 EPYCs will be more efficient
-
hyc
yes, but to make an impact they needed to be more than 2x better. that was the threshold for GPUs to still be competitive on ETH
-
sech1
So nothing will change, they're already on the network
-
sech1
and mining
-
hyc
they're nowhere near that threshold
-
sech1
the ad says "multiple cryptocurrencies", so it's not even specialized. It's probably some custom RISC-V chips, but they're just regular CPUs
-
hyc
yep
-
hyc
but that's actually impressive for RISC-V to match AMD efficiency
-
sech1
they probably took some shortcuts
-
sech1
like 2 MB cache per core, but it's not shared between cores
-
sech1
which will save some energy and a ton of area
-
hyc
good point
-
hyc
yeah, plenty of easy optimizations if they don't need to run general workloads
-
kico
I guess that "whoever designs a randomx chip will help in advancing cpus" is still true but I never expected for riscV :D
-
hyc
lol it kinda makes sense, no licensing restrictions
-
sech1
risc-v only because no need to pay fees
-
hyc
and it was the new hotness already
-
sech1
they didn't want to pay ARM fees :D
-
kico
:)
-
kico
all gud as long as they kinda contribute to riscV development iGuess
-
hyc
might be time for me to order a risc-v box from aliexpress
-
hyc
kico: wouldn't hold my breath on that
-
kico
yeah sure
-
kico
being optimistic here iGuess
-
hyc
but would be funny to see any bitmaintech names in LLVM/clang/gcc contributions
-
sech1
btw, back in early 2022 those "ASIC" workers we saw, they all had 250-300 kh/s reported hashrate on nanopool
-
sech1
I guess after 2 years of operation, they had to disable some of the units and reduce to 212 kh guarantee
-
hyc
overclocked and died :P
-
kico
does this mean that "pow fork" is delayed for the time being?
-
hyc
this has no impact on pow decisions
-
selsta
The partial verification changes are useful for other reasons.
-
kico
sure I mean no need for a "urgent fork" ?
-
hyc
yeah, the double hash to improve verification speed is worthwhile all on its own
-
selsta
I don't think there were any plans for an emergency PoW change
-
kico
ok cool I got the wrong impression my bad :)
-
hyc
at this point tweaking the algo won't stop anyone, they're obviously using CPUs now so they can just update their firmware
-
sech1
I doubt tweaks will stop these devices, they're proper CPUs from the looks of things
-
kico
yeah but we should not care about them anyway
-
hyc
the only things we could change that would make a substantial difference would be the on-chip cache requirements, and that would hurt all CPUs as well
-
DataHoarder
moar L3, time to force multi threaded communication and atomics!
-
sech1
of course, we can target tweaks to kill these specific devices
-
sech1
like increase L3 until it exceeds what they have
-
kico
sure but do we want to ?
-
sech1
No need
-
kico
not like they're super efficient
-
sech1
Like I said, they've been mining for almost 2 years now
-
hyc
it would be fun to see their 2+ years of effort poof
-
sech1
and they don't have superior efficiency
-
hyc
but anything we did like that would only have a temporary effect
-
kico
hyc, they already did ROI by now
-
sech1
it's better that we make tweaks that make regular CPUs more efficient
-
sech1
like my CFROUND tweak
-
sech1
it will make Zen4 more efficient than these ASICs
-
kico
yeah I think we should care for regular users and not jihan
-
sech1
So far, RandomX works as it's been designed. If we do tweaks, we should focus on current and next generation CPUs.
-
hyc
agreed
-
m-relay
<xfedex:matrix.org> Ryzen 9 5950X (Zen 3, launch date 2020) is more power efficient than this ASIC.
-
hyc
I doubt they spent any effort on tuning the chips, and all their effort was on cramming a bunch of cores into a single case.
-
sech1
The only question now is the price
-
m-relay
<xfedex:matrix.org> I estimate that it would have to cost ~$3500 or less to be worth buying that ASIC over Ryzen CPUs
-
hyc
probably the best contriution they'd make to the world is in their physical build and cooling layout
-
sech1
They have ~2000 of those ASICs mining now
-
m-relay
<k4r4b3y:karapara.net> How did you get to that estimate?
-
sech1
judging by the hashrate of that ASIC miner (we know now it was Bitmain)
-
sech1
they have ~17% of the network
-
sech1
so around 400-450 MH/s
-
sech1
Not sure if they ever got their money back :D
-
hyc
all the more reason for them to start selling :P
-
m-relay
<xfedex:matrix.org> sech1: sorry, what is your CFROUND tweak?
-
sech1
it's a tweak that changes how often CFROUND instruction is triggered
-
sech1
it can boost Ryzen hashrate by up to 10% without changing anything else in RandomX
-
m-relay
<xfedex:matrix.org> is there any link for it?
-
sech1
so we had 10% "free" hashrate all this time
-
sech1
No link, but it was discussed in this channel before
-
m-relay
-
hyc
hmmm. I wonder - would it be more efficient to add pool support to monerod (so that its internal miner could work with p2pool) or
-
hyc
add hasher rpc to xmrig - so that it could do verification for both monerod and p2pool
-
gingeropolous
so even after all the fuss in the original monero asic war, an asic company *still* decided to build and mine in secret
-
hyc
lol, of course.
-
hyc
that's what they do, why would they change
-
m-relay
<xfedex:matrix.org> hyc: the simplest thing to do which does not require any code change is running monerod with MONERO_RANDOMX_FULL_MEM and running p2pool with --no-randomx
-
gingeropolous
and i doubt they even made these things capable of running anode, even though is a damn CPU
-
gingeropolous
true milkers, not adding anything to the ecosystem
-
m-relay
<xfedex:matrix.org> gingeropolous: they OBVIOUSLY didn't
-
hyc
xfedex: yes of course. I wrote that code.
-
gingeropolous
lulz, that nitter page; "guess the price". they are trying to find what the market will tolerate to buy their burnt out silicon
-
hyc
I use it 24/7 on my rockpro64. but I currently am not running xmrig on it because there wouldn't be enough RAM.
-
m-relay
<xfedex:matrix.org> I think the miner integrated in p2pool has performance similar to xmrig
-
m-relay
<xfedex:matrix.org> Does your device have enough RAM to run monerod without full memory and p2pool with RandomX fast mode?
-
hyc
probably. but that's still a couple hundred MB I'd prefer not to spend. anything that takes away from available FS cache hurts monerod perf
-
sech1
and memory limited devices, it's best to have full dataset in monerod and make everything else use calc_pow RPC call
-
sech1
*on memory
-
sech1
p2pool integrated miner has 5-10% lower performance even if you help it with manual MSR mod
-
sech1
because there are many code-level optimizations in xmrig
-
hyc
so... it might be worthwhile to add calc_pow RPC to xmrig itself, and point both monerod and p2pool at it
-
sech1
that's kind of backwards
-
hyc
why? let the fastest code do all of the hash computations
-
sech1
xmrig optimizations were always designed to make it faster, but never cared about being 100% correct all the time
-
hyc
ah
-
hyc
ok never mind
-
sech1
granted, it's correct now but I'm not sure I can give a guarantee :D
-
hyc
then back to the earlier idea, let monerod's miner work with p2pool
-
sech1
because I don't remember exactly, but at some point I considered optimizations that would make it 1% faster at a cost of 0.1% invalid hashes, for example
-
DataHoarder
-f-unsafe-randomx-optimizations
-
sech1
well, just in case we want to brick this ASIC, I already found an instruction that's available on x86 and ARM (not all x86 and ARM, but many), but 100% is not there on that RISC-V chip.
-
DataHoarder
on *that* risc-v chip?
-
DataHoarder
do we know what they have, or custom design? given extensions are plenty
-
sech1
If they have risc-v chip, I know what they *don't* have :P
-
sech1
risc-v is an open standard, after all
-
sech1
and an instruction I picked, it's not even a finalized draft in risc-v, lol
-
sech1
*it's not ratified yet
-
sech1
and considering that they physically created their ASICs in 2021... It's 10000% not there
-
DataHoarder
yeah, just saying that the standard includes instructions but there are many custom extensions on these risc-v chips out there
-
DataHoarder
they probably have none though :D
-
sech1
They use RV64GC+Zk at best, which leaves a lot of unsupported instructions
-
sech1
RV64GC is a "standard" 64-bit RISC instruction set, Zk is needed for AES (I think)
-
DataHoarder
yeah, unless they placed it in the non-standard extension in the "Guaranteed Non-Standard Encoding Space"
-
sech1
I bet they used as much standard stuff as possible to reduce costs
-
Inge
1350w? What is the claimed performance of the thing?
-
sech1
212 kh/s
-
sech1
about the same efficiency as Ryzen 5950X/7950X
-
Inge
I mean... I'm partial to RISC-V getting a leg up :D
-
sech1
On the other hand, adding an instruction that's not ratified in risc-v yet, will make trouble for all risc-v systems for the foreseeable future, not just for this ASIC. It's not ideal.
-
sech1
It will not make RandomX on RISC-V impossible, but it will make it noticeably slower
-
m-relay
<polar9669:matrix.org> So are we now going to favour particular cpu architectures ? Because someone made cpus to mine monero
-
DataHoarder
considering possibilities doesn't mean they will be pushed for at all
-
gingeropolous
yeah, i mean, randomx is cpu-bound, and this RISC-V system is CPUs. I don't see the sense in modding the PoW to counter this development. I think time has already addressed the concern, and will continue to.