17:23:25 <sech1> good news everyone, a long standing bug has been found and fixed: https://github.com/tevador/RandomX/pull/281
17:35:37 <hyc> https://youtu.be/0oRlVKdOzmU
17:36:28 <hyc> long-standing bug that only affected Mac aarch64
19:31:53 <fvok4> 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) ?
19:33:04 <fvok4> 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)
19:33:24 <m-relay> <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?
19:33:26 <fvok4> I expect it to be in the order of milliseconds, but this is just a guess.
19:33:36 <m-relay> <j​effro256:monero.social> or do you mean just the time it takes to verify ring signature
19:33:41 <rbrunner> I think everybody around here needing such info would just grab the source code, add some timing code, compile, run
19:34:02 <fvok4> jefrro256, if you can provide both times that would be even better!
19:34:39 <m-relay> <j​effro256:monero.social> For the latter you can run the performance tests
19:34:42 <fvok4> rbrunner, an official source, academic paper, or related source would be better in my case
19:35:06 <fvok4> jeffro256, where I can find instructions to run those tests locally?
19:35:16 <rbrunner> I understand, I just doubt somebody did this, and published
19:36:07 <fvok4> if nobody published something about it, then it will be extra work for me, which I wanted to avoid
19:38:07 <m-relay> <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`
19:38:21 <fvok4> excellent, thanks!
19:39:09 <m-relay> <j​effro256:monero.social> You also need to verify bulletproofs for a transaction so check out the case `test_bulletproof_plus`
19:57:44 <m-relay> <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`
20:01:39 <fvok4> thanks, that is what I need
20:03:34 <m-relay> <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
20:03:44 <m-relay> <j​effro256:monero.social> But its a good rough measurement otherwise