-
selsta
-
selstacould someone reply here? can mining result in monerod taking up 26GB RAM and is the crash related to their CPU?
-
sech1My monerod is not mining and it takes 17 GB of RAM right now
-
sech1It has been running for weeks though
-
selstamine uses less than 1GB RAM
-
selstasech1: v0.16?
-
sech10.15.0.0
-
sech1I'm very conservative, lol
-
selstathat’s quite old :D
-
sech1if it works, don't touch it (c)
-
moneromoooI see no mention of a crash.
-
selstathey wrote > One time I saw 'error: verification failed' just before it crashed.
-
selstathough no logs
-
sech1It's probably early 1st-gen Ryzen hardware bug
-
sech1when mining RandomX
-
selstadid xmrig implemet a fix for it?
-
sech1yes
-
sech1more a workaround
-
sech1because it still crashes, but xmrig just skips a hash where it crashes
-
selstaok well tell them to use xmrig for mining
-
sech1"I was trying to start xmrig to solomine for a bit to my own local deamon, but it wouldn't start mining. The problem appears to be that there's not enough RAM available."
-
selsta
-
selstafrom -pools
-
selstagone already
-
tevadorremoving this one if improved performance by 25%: tevador/hashx b612cd2
-
tevadoramazing
-
hycnice. branches suck. did it get replaced by a conditional move or something?
-
tevadoryep
-
tevadorit was a typical unpredictable branch causing a lot of mispredictions
-
hyclooks like available is strictly a toggle between 1 and 0. could also get rid of the ?: operator and just use available * i.
-
tevadorI checked the generated machine code, compiler uses cmovne, which seems to be pretty efficient and takes just 1 cycle compared to 3 cycles for multiplication
-
hycfair enough