16:05:24 <br-m> <jpk68:matrix.org> Are there any benchmarks of CryptoNightR JIT performance compared to the interpreter?
17:53:13 <sech1> Now that's a name I haven't heard in a loong time...
17:53:37 <sech1> CryptonightR has almost the same hashrate as regular Cryptonight
17:53:52 <sech1> Interpreter is 2-3x slower, iirc
17:55:28 <br-m> <jpk68:matrix.org> Thanks. I want to try and work on ARM/RISC-V backends for the JIT eventually, just have to become less bad at assembly first...
17:56:32 <br-m> <jpk68:matrix.org> Cuprate's pure Rust implementation of CryptoNight (all of the variants) doesn't have a JIT at all for v4/R currently
19:29:44 <DataHoarder> I implemented cryptonight (and its variants for monero) on https://git.gammaspectra.live/P2Pool/consensus/src/branch/master/monero/cryptonight as interpreter (with an optimized switch loop for R) with some mild assembly/intrinsics for some operations, for most block verification purposes this was enough, same for opening/closing derived wallet
19:29:44 <DataHoarder> files
19:31:19 <DataHoarder> CryptonightR was used on a small interval to cover some time until RandomX was upgraded to, so maybe that's fine for the verification usecase?
20:06:49 <br-m> <boog900> Yeah for us we don't really need a JIT. Fast sync will skip it all together and full verification sync is more than fast enough compared to monerod.