good news everyone, a long standing bug has been found and fixed: tevador/RandomX #281

long-standing bug that only affected Mac aarch64

hello, where I can find information about the average time a monero node, using consumer-grade cpu, takes to verify a RCCTypeBulletproof2 transaction (which is currently the standard) ?

also, about the time a client would normally take to build a transactions (just build, not the broadcast time, which is affected by the network)

<j​effro256:monero.social> Depends on what you mean by verify: do you mean the time it takes for `monerod` to see the transaction, deserialize, run semantics test it, fetch required input context information, then do ring sig tests?

I expect it to be in the order of milliseconds, but this is just a guess.

<j​effro256:monero.social> or do you mean just the time it takes to verify ring signature

I think everybody around here needing such info would just grab the source code, add some timing code, compile, run

jefrro256, if you can provide both times that would be even better!

<j​effro256:monero.social> For the latter you can run the performance tests

rbrunner, an official source, academic paper, or related source would be better in my case

jeffro256, where I can find instructions to run those tests locally?

I understand, I just doubt somebody did this, and published

if nobody published something about it, then it will be extra work for me, which I wanted to avoid

<j​effro256:monero.social> To run the performance tests locally, compile the source code, then go to the build directory and run `tests/performance_tests/performance_tests`. The relevant test case is `test_sig_clsag`

excellent, thanks!

<j​effro256:monero.social> You also need to verify bulletproofs for a transaction so check out the case `test_bulletproof_plus`

<j​effro256:monero.social> As for the in-practice time to verify a transaction, run `monerod` with `--log-level perf.txpool:INFO`, and filter for `add_tx`

thanks, that is what I need

<j​effro256:monero.social> Note that this entries will also include the times it takes to check that a transaction is *invalid*. So if you daemon is getting spammed with invalid transactions, this will throw off your data

<j​effro256:monero.social> But its a good rough measurement otherwise